09 Jul, 2015

1 commit


01 Jul, 2015

2 commits

  • Now zynq spi driver platform data is controlled by devicetree,
    enable the status by saying "okay" on respective board dts to use
    the devicetree generated platdata.

    Ex:
    &spi1 {
    status = "okay";
    };

    Signed-off-by: Jagan Teki
    Acked-by: Simon Glass
    Cc: Michal Simek
    Cc: Siva Durga Prasad Paladugu
    Tested-by: Jagan Teki

    Jagan Teki
     
  • This patch adds zynq spi controller nodes in zynq-7000.dtsi.

    Signed-off-by: Jagan Teki
    Acked-by: Simon Glass
    Cc: Michal Simek
    Cc: Siva Durga Prasad Paladugu
    Tested-by: Jagan Teki

    Jagan Teki
     

11 Jun, 2015

1 commit

  • Some AVR32 boards were dropped by the following commits:
    9eb45aabe078 (avr32: delete non generic board favr-32-ezkit)
    e36930764471 (avr32: delete non generic board hammerhead)
    c62d2f8fc5c6 (avr32: delete non generic board mimc200)
    e5354b8a9e2a (avr32: delete non generic board's atstk100{3, 4, 6})

    Acked-by: Andreas Bießmann
    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

08 Jun, 2015

1 commit

  • These defines for a 2nd autoboot stop and delay string are nearly unused. Only
    sc3 defines CONFIG_AUTOBOOT_DELAY_STR2. And a patch to remove this most likely
    unmaintained board is also posted to the list.

    By removing these defines the code will become cleaner and moving the remaining
    compile options to Kconfig will get easier.

    Signed-off-by: Stefan Roese
    Reviewed-by: Tom Rini
    Reviewed-by: Simon Glass
    Cc: Wolfgang Denk
    Cc: Heiko Schocher

    Stefan Roese
     

06 Jun, 2015

1 commit


05 Jun, 2015

1 commit

  • Before device-tree, the device serial number used to be passed to the kernel
    using ATAGs (on ARM). This is now deprecated and all the handover to the kernel
    should now be done using device-tree. Thus, this passes the serial-number
    property to the kernel using the serial-number property of the root node, as
    expected by the kernel.

    The serial number is a string that somewhat represents the device's serial
    number. It might come from some form of storage (e.g. an eeprom) and be
    programmed at factory-time by the manufacturer or come from identification
    bits available in e.g. the SoC.

    Signed-off-by: Paul Kocialkowski
    Reviewed-by: Simon Glass

    Paul Kocialkowski
     

04 Jun, 2015

5 commits


28 May, 2015

2 commits


26 May, 2015

1 commit


25 May, 2015

2 commits

  • Prior to this commit, ZC702 and ZC706 shared the same configuration
    and were built as follows:

    ZC702: make zynq_zc70x_defconfig && make
    ZC706: make zynq_zc70x_defconfig && make DEVICE_TREE=zynq-zc706

    This commit introduces separate configuration for them, which makes
    the next commit much easier.

    Going forward, the recommended build commands are:

    ZC702: make zynq_zc702_defconfig && make
    ZC706: make zynq_zc706_defconfig && make

    Although the old work flow is still supported, CONFIG_TARGET_ZC70X
    has been marked as deprecated. If used, the warning message is
    shown to prompt users to switch to the new scheme.

    Signed-off-by: Masahiro Yamada
    Acked-by: Joe Hershberger
    Signed-off-by: Michal Simek

    Masahiro Yamada
     
  • This commit allows users to enable/disable the Freescale NFC
    controller found in systems like Vybrid (VF610), MPC5125, MCF54418
    or Kinetis K70 via Kconfig with more detailed help docs.

    Signed-off-by: Stefan Agner
    Acked-by: Stefano Babic
    [scottwood: updated vf610twr_nand_defconfig]
    Signed-off-by: Scott Wood

    Stefan Agner
     

21 May, 2015

2 commits


20 May, 2015

2 commits


16 May, 2015

2 commits


15 May, 2015

7 commits

  • This commit adds emulation of sandbox PMIC device, which includes:
    - PMIC I2C emulation driver
    - PMIC I/O driver (UCLASS_PMIC)
    - PMIC regulator driver (UCLASS_REGULATOR)

    The sandbox PMIC has 12 significant registers and 4 as padding to 16 bytes,
    which allows using 'i2c md' command with the default count (16).

    The sandbox PMIC provides regulators:
    - 2x BUCK
    - 2x LDO

    Each, with adjustable output:
    - Enable state
    - Voltage
    - Current limit (LDO1/BUCK1 only)
    - Operation mode (different for BUCK and LDO)

    Each attribute has it's own register, beside the enable state, which depends
    on operation mode.

    The header file: sandbox_pmic.h includes PMIC's default register values,
    which are set on i2c pmic emul driver's probe() method.

    Signed-off-by: Przemyslaw Marczak
    Acked-by: Simon Glass
    Tested on sandbox:
    Tested-by: Simon Glass

    Przemyslaw Marczak
     
  • This commit cleanups the PMIC framework documentation.

    Signed-off-by: Przemyslaw Marczak
    Acked-by: Simon Glass
    Tested on sandbox:
    Tested-by: Simon Glass

    Przemyslaw Marczak
     
  • Since this framework is still under the construction, the main
    documentation is kept in the header files.

    Signed-off-by: Przemyslaw Marczak
    Acked-by: Simon Glass

    Przemyslaw Marczak
     
  • This driver implements regulator operations for fixed Voltage/Current
    value regulators. beside the standard regulator constraints, which are
    put into the uclass platform data, a typical fixed regulator node provides
    few additional properties like:
    - gpio
    - gpio-open-drain
    - enable-active-high
    - startup-delay-us
    The only 'gpio' is used by this driver and is kept in structure of type
    'fixed_regulator_platdata', as a device platform data (dev->platdata).

    The driver implements:
    - get_value
    - get_current
    - get_enable
    - set_enable

    The regulator calls and commands can be used for fixed-regulator devices,
    and the proper error will be returned for prohibited.

    Signed-off-by: Przemyslaw Marczak
    Acked-by: Simon Glass

    Przemyslaw Marczak
     
  • This commit adds support to MAX77686 regulator driver,
    based on a driver model regulator's API. It implements
    almost all regulator operations, beside those for setting
    and geting the Current value.
    For proper bind and operation it requires the MAX77686 PMIC driver.

    New file: drivers/power/regulator/max77686.c
    New config: CONFIG_DM_REGULATOR_MAX77686

    Signed-off-by: Przemyslaw Marczak
    Acked-by: Simon Glass

    Przemyslaw Marczak
     
  • This is the implementation of driver model PMIC driver.
    The max77686 PMIC driver implements read/write operations and driver
    bind method - to bind its childs.

    This driver will try to bind the regulator devices by using it's child
    info array with regulator prefixes and driver names. This should succeed
    when compatible regulator driver is compiled. If no regulator driver found,
    then the pmic can still provide read/write operations, and can be used with
    PMIC function calls.

    Signed-off-by: Przemyslaw Marczak
    Acked-by: Simon Glass

    Przemyslaw Marczak
     
  • This commit introduces the implementation of dm regulator API.
    Device tree support allows for auto binding. And by the basic
    uclass operations, it allows to driving the devices in a common
    way. For detailed informations, please look into the header file.

    Core files:
    - drivers/power/regulator-uclass.c - provides regulator common functions api
    - include/power/regulator.h - define all structures required by the regulator

    Changes:
    - new uclass-id: UCLASS_REGULATOR
    - new config: CONFIG_DM_REGULATOR

    Signed-off-by: Przemyslaw Marczak
    Acked-by: Simon Glass

    Przemyslaw Marczak
     

14 May, 2015

3 commits


13 May, 2015

1 commit

  • Remove board support for afeb9260, tny_a9260, and sbc35_a9g20.

    They have not been converted into Generic Board yet.
    See doc/README.generic-board for details.

    Signed-off-by: Masahiro Yamada
    Cc: Sergey Lapin
    Cc: Albin Tonnerre
    Cc: Andreas Bießmann

    Masahiro Yamada
     

10 May, 2015

1 commit


08 May, 2015

1 commit


07 May, 2015

1 commit


06 May, 2015

1 commit


05 May, 2015

1 commit


30 Apr, 2015

1 commit