29 Oct, 2010

40 commits

  • Implement support for controlling WM831x and WM832x devices using SPI.

    Signed-off-by: Mark Brown
    Signed-off-by: Samuel Ortiz

    Mark Brown
     
  • In preparation for the addition of SPI support for the WM831x move the I2C
    specific code into a separate file with a separate Kconfig option so the
    I2C support can be excluded from the build.

    Also update the 1133-EV1 PMIC module support for SMDK6410 to use the new
    symbol.

    Signed-off-by: Mark Brown
    Signed-off-by: Samuel Ortiz

    Mark Brown
     
  • DEBUG and VERBOSE_DEBUG are not used.

    Reported-by: David Jander
    Signed-off-by: Samuel Ortiz

    Samuel Ortiz
     
  • When enabled is false, clear BIT(engine) of JZ_REG_ADC_ENABLE register.

    Signed-off-by: Axel Lin
    Acked-by: Lars-Peter Clausen
    Signed-off-by: Samuel Ortiz

    Axel Lin
     
  • The interface for this device should be identical to that of the
    TPS658521A.

    Signed-off-by: Andrew Chew
    Acked-by: Mike Rapoport
    Signed-off-by: Samuel Ortiz

    Andrew Chew
     
  • Fixes following sparse warnings for twl4030 and twl6030 irq files.

    drivers/mfd/twl4030-irq.c:783:5: warning: symbol 'twl4030_init_irq' was not
    declared. Should it be static?
    drivers/mfd/twl4030-irq.c:863:5: warning: symbol 'twl4030_exit_irq' was not
    declared. Should it be static?
    drivers/mfd/twl4030-irq.c:873:5: warning: symbol 'twl4030_init_chip_irq' was
    not declared. Should it be static?

    drivers/mfd/twl6030-irq.c:226:5: warning: symbol 'twl6030_init_irq' was not
    declared. Should it be static?
    drivers/mfd/twl6030-irq.c:290:5: warning: symbol 'twl6030_exit_irq' was not
    declared. Should it be static?

    Signed-off-by: G, Manjunath Kondaiah
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: Tony Lindgren
    Cc: Nishanth Menon
    Signed-off-by: Samuel Ortiz

    G, Manjunath Kondaiah
     
  • max8998_pmic_probe:
    - modified to check if valid pins are defined at platform
    data
    - maximal voltage values (predefined at platform data) are uploaded to
    max8998 device

    max8998_set_voltage_buck:
    - BUCK1/2 voltages change between values already defined
    - Checks if valid GPIO pins are passed from platform data
    - If requested voltage cannot be satisfied from already defined values,
    then one of free slots is used
    - Predefined maximum voltages (as defined at platform data) are always
    available

    Signed-off-by: Lukasz Majewski
    Signed-off-by: Kyungmin Park
    Acked-by: Mark Brown
    Acked-by: Liam Girdwood
    Signed-off-by: Samuel Ortiz

    Lukasz Majewski
     
  • Signed-off-by: Lukasz Majewski
    Signed-off-by: Kyungmin Park
    Acked-by: Mark Brown
    Acked-by: Liam Girdwood
    Signed-off-by: Samuel Ortiz

    Lukasz Majewski
     
  • BUCK1/2 internal voltages and indexes defined in the struct max8998_data
    max_get_voltage_register now uses index values to chose proper register
    More generic BUCK1/2 registers names provided

    Signed-off-by: Lukasz Majewski
    Signed-off-by: Kyungmin Park
    Acked-by: Mark Brown
    Acked-by: Liam Girdwood
    Signed-off-by: Samuel Ortiz

    Lukasz Majewski
     
  • Signed-off-by: Lukasz Majewski
    Signed-off-by: Kyungmin Park
    Acked-by: Mark Brown
    Acked-by: Liam Girdwood
    Signed-off-by: Samuel Ortiz

    Lukasz Majewski
     
  • Signed-off-by: Lukasz Majewski
    Signed-off-by: Kyungmin Park
    Acked-by: Mark Brown
    Acked-by: Liam Girdwood
    Signed-off-by: Samuel Ortiz

    Lukasz Majewski
     
  • The chip TRM documentation contradicts itself about this bit, page 174
    of swcu050e says bit should be 0 for clear-on-read behavior, while
    page 487 says it should be 1. Testing shows it should be 1, so set
    the .set_cor flag accordingly. This is needed for upcoming BCI
    charging driver to function.

    Signed-off-by: Grazvydas Ignotas
    Acked-by: Tony Lindgren
    Signed-off-by: Samuel Ortiz

    Grazvydas Ignotas
     
  • When the cell data_size is 0, the resulting platform_data pointer will be
    set to ZERO_SIZE_PTR. That could be misleading for device drivers running
    a NULL check on thei platform_data pointer before dereferencing it.

    Signed-off-by: Brian Harring
    Signed-off-by: Samuel Ortiz

    Brian Harring
     
  • Now that we have twl4030 charger driver, add back it's platform_data
    (which was removed by f7ea2dc59ed46dcd0f1cfaccda02211f4507207b
    as unused).

    Signed-off-by: Grazvydas Ignotas
    Acked-by: Tony Lindgren
    Signed-off-by: Samuel Ortiz

    Grazvydas Ignotas
     
  • The mfd driver for MC13783 recently got support for MC13892 and was
    renamed accordingly from mc13783-core to mc13xxx-core. Do the same for
    rtc-mc13783.

    The only relevant change is to use platform id's to tell the platform bus
    that this driver is responsible for mc13892-rtc devices, too.

    Acked-by: Alessandro Zummo
    Signed-off-by: Uwe Kleine-König
    Signed-off-by: Samuel Ortiz

    Uwe Kleine-König
     
  • Adding card detect callback function and card detect configuration
    function for MMC1 Controller on OMAP4.

    Card detect configuration function does initial configuration of the
    MMC Control & PullUp-PullDown registers of Phoenix.

    For MMC1 Controller, card detect interrupt source is
    twl6030 which is non-gpio. The card detect call back function provides
    card present/absent status by reading MMC Control register present
    on twl6030.

    Since OMAP4 doesn't use any GPIO line as used in OMAP3 for card detect,
    the suspend/resume initialization which was done in omap_hsmmc_gpio_init
    previously is moved to the probe thus making it generic for both OMAP3 &
    OMAP4.

    Cc: Tony Lindgren
    Cc: Andrew Morton
    Cc: Madhusudhan Chikkature
    Cc: Adrian Hunter
    Signed-off-by: Kishore Kadiyala
    Signed-off-by: Samuel Ortiz

    kishore kadiyala
     
  • mc13892 is the companion PMIC for Freescale's i.MX51. It's similar enough
    to mc13782 to support it in a single driver.

    This patch introduces enough compatibility cruft to keep all users of the
    superseded mc13783 driver unchanged.

    Signed-off-by: Uwe Kleine-König
    Signed-off-by: Samuel Ortiz

    Uwe Kleine-König
     
  • The last user is gone since v2.6.34-rc1~40

    Signed-off-by: Uwe Kleine-König
    Signed-off-by: Samuel Ortiz

    Uwe Kleine-König
     
  • The regulator driver was converted to get the needed data directly from
    platform_data by

    a10099b (regulator/mc13783: various cleanups)

    so regulators and num_regulators can go away. Then apart from the flag
    indicating that the adc does a conversion, flags is only a copy of the
    flags member of platform_data. This flag isn't needed to be returned by
    mc13783_get_flags, so mc13783_get_flags now gets the flags from
    platform_data, too and the driver private member is renamed for clearity.

    Signed-off-by: Uwe Kleine-König
    Signed-off-by: Samuel Ortiz

    Uwe Kleine-König
     
  • This is needed for supporting the upcoming VX855 camera and OLPC DCON
    drivers, as well as the advanced viafb features on non-OLPC hardware
    based on this chip.

    Based on earlier work by Harald Welte.

    Signed-off-by: Daniel Drake
    Signed-off-by: Samuel Ortiz

    Daniel Drake
     
  • This device has GPIO, SPI and I2C capabilities.

    The hardware can be found in the OLPC XO-1.5 laptop.

    Based on earlier work by Harald Welte.

    Signed-off-by: Daniel Drake
    Signed-off-by: Samuel Ortiz

    Daniel Drake
     
  • The upcoming VIA VX855 MFD driver needs to communicate resources
    to subdevices where the resources may be claimed by ACPI.

    Add a flag to mfd_cell to request that resources are not policed.

    Signed-off-by: Daniel Drake
    Signed-off-by: Samuel Ortiz

    Daniel Drake
     
  • Remove original 3-second ONKEY event. Detect ONKEY changing event directly.
    So both UP and DOWN event of ONKEY in max8925 are monitered.

    Signed-off-by: Haojian Zhuang
    Cc: Dmitry Torokhov
    Signed-off-by: Samuel Ortiz

    Haojian Zhuang
     
  • 88pm860x supports auto-blink LED in hardware. It messed with
    timer trigger. Now disable the auto-blink function.

    Signed-off-by: Haojian Zhuang
    Cc: Richard Purdie
    Signed-off-by: Samuel Ortiz

    Haojian Zhuang
     
  • The WM8325 is a PMIC for low power, high performance applications. From
    a software point of view the device is identical to the WM8320, all the
    differences are at the hardware level.

    Signed-off-by: Mark Brown
    Signed-off-by: Samuel Ortiz

    Mark Brown
     
  • Otherwise sparse warns about a public symbol with no declaration and
    the compiler can't spot if the callers and users have different signatures
    for the function.

    Signed-off-by: Mark Brown
    Signed-off-by: Samuel Ortiz

    Mark Brown
     
  • Fixes below sparse warning.

    drivers/mfd/twl-core.c:258:20: warning: symbol 'twl_map' was not declared. Should it be static?

    Signed-off-by: G, Manjunath Kondaiah
    Cc: linux-arm-kernel@lists.infradead.org
    Cc: Tony Lindgren
    Cc: Nishanth Menon
    Signed-off-by: Samuel Ortiz

    G, Manjunath Kondaiah
     
  • This patch defines platform data for the ks8842 int the timberdale
    MFD.
    The platform data contains DMA channels to be used by the driver.

    Signed-off-by: Richard Röjfors
    Signed-off-by: Samuel Ortiz

    Richard Röjfors
     
  • Add PM helpers to STMPE and add support to enable wakeup from low power
    states

    Acked-by: Rabin VINCENT
    Acked-by: Linus WALLEIJ
    Signed-off-by: Sundar Iyer
    Signed-off-by: Samuel Ortiz

    Sundar Iyer
     
  • Free allocated memory. Call stmpe_disable() if it was enabled.

    Signed-off-by: Vasiliy Kulikov
    Acked-by: Wolfram Sang
    Acked-by: Rabin Vincent
    Signed-off-by: Samuel Ortiz

    Vasiliy Kulikov
     
  • msp430 being a bool, it will only work with I2C=y

    Signed-off-by: Samuel Ortiz

    Samuel Ortiz
     
  • This patch add a dependancy for ab8500-core driver so as to depend on
    u8500 platform.

    This patch also fixes the build issues(powerpc_allyesconfig) for the
    patch 03f582a93ecca6e9584b622570022abf08ed03ec (misc: Add ab8500 pwm
    driver)

    Signed-off-by: Arun Murthy
    Acked-by: Linus Walleij
    Signed-off-by: Samuel Ortiz

    Arun Murthy
     
  • Add support for enabling and disabling tps6586x subdevice interrupts

    Signed-off-by: Gary King
    Acked-by: Mike Rapoport
    Signed-off-by: Samuel Ortiz

    Gary King
     
  • This patch adds the choice of accessing the AB8500 registers
    via prcmu I2C. Access either via SPI or I2C is supported.

    Signed-off-by: Mattias Wallin
    Acked-by: Linus Walleij
    Signed-off-by: Samuel Ortiz

    Mattias Wallin
     
  • This patch adds the possibility to read and write registers
    via the debug_fs. It also adds ranges of registers sorted by bank
    which makes it possible to read all defined registers in a bank.

    Signed-off-by: Mattias Wallin
    Acked-by: Linus Walleij
    Reviewed-by: Mark Brown
    Signed-off-by: Samuel Ortiz

    Mattias Wallin
     
  • Chipid of 88pm8607 is 0x40 or 0x50.

    Signed-off-by: Haojian Zhuang
    Signed-off-by: Samuel Ortiz

    Haojian Zhuang
     
  • This patch adds a Pulse Width Modulation driver for Analog Baseband
    Chip AB8500.

    Signed-off-by: Arun Murthy
    Acked-by: Linus Walleij
    Acked-by: Mike Rapoport
    Signed-off-by: Samuel Ortiz

    Arun Murthy
     
  • This patch makes the ab8500 mixed signal chip expose the same
    interface for register access as the ab3100, ab3550 and ab5500 chip.
    The ab8500_read() and ab8500_write() is removed and replaced with
    abx500_get_register_interruptible() and
    abx500_set_register_interruptible().

    Signed-off-by: Mattias Wallin
    Acked-by: Linus Walleij
    Acked-by: Mark Brown
    Signed-off-by: Samuel Ortiz

    Mattias Wallin
     
  • This patch removes the requirement that gpio base be supplied in
    platform data.

    Signed-off-by: Virupax Sadashivpetimath
    Acked-by: Linus Walleij
    Acked-by: Wolfram Sang
    Signed-off-by: Samuel Ortiz

    Virupax Sadashivpetimath
     
  • Adjust the tmio_mmc block size check to accept 2-byte requests in 4-bit
    mode if the hardware supports it.

    Tested with the SDHI hardware block included in sh7724.

    Signed-off-by: Yusuke Goda
    Signed-off-by: Matt Fleming
    Acked-by: Magnus Damm
    Tested-by: Arnd Hannemann
    Signed-off-by: Samuel Ortiz

    Yusuke Goda