24 Nov, 2011

1 commit

  • With device tree support for regulators, its needed that the
    regulator_dev->dev device has the right of_node attached.
    To be able to do this add an additional parameter to the
    regulator_register() api, wherein the dt-adapted driver can
    then pass this additional info onto the regulator core.

    Signed-off-by: Rajendra Nayak
    Signed-off-by: Mark Brown

    Rajendra Nayak
     

27 May, 2011

1 commit


26 Apr, 2011

1 commit

  • Using C line continuation inside format strings is error prone.
    Clean up the unintended whitespace introduced by misuse of \.
    Neaten correctly used line continations as well for consistency.

    drivers/scsi/arcmsr/arcmsr_hba.c has these errors as well,
    but arcmsr needs a lot more work and the driver should likely be
    moved to staging instead.

    Signed-off-by: Joe Perches
    Acked-by: Randy Dunlap
    Signed-off-by: Jiri Kosina

    Joe Perches
     

27 Mar, 2011

1 commit


14 Jan, 2011

2 commits

  • The previous driver did not support BUCK1-DVS3, BUCK1-DVS4, and
    BUCK2-DVS2 modes. This patch adds such modes and an option to block
    setting buck1/2 voltages out of the preset values.

    Signed-off-by: MyungJoo Ham
    Signed-off-by: Kyungmin Park
    Acked-by: Mark Brown
    Signed-off-by: Samuel Ortiz

    MyungJoo Ham
     
  • The first releases of LP3974 have a large delay in RTC registers,
    which requires 2 seconds of delay after writing to a rtc register
    (recommended by National Semiconductor's engineers)
    before reading it.

    If "rtc_delay" field of the platform data is true, the rtc driver
    assumes that such delays are required. Although we have not seen
    LP3974s without requiring such delays, we assume that such LP3974s
    will be released soon (or they have done so already) and they are
    supported by "lp3974" without setting "rtc_delay" at the platform
    data.

    This patch adds delays with msleep when writing values to RTC registers
    if the platform data has rtc_delay set.

    Signed-off-by: MyungJoo Ham
    Signed-off-by: Kyungmin Park
    Reviewed-by: Mark Brown
    Signed-off-by: Samuel Ortiz

    MyungJoo Ham
     

12 Jan, 2011

2 commits


29 Oct, 2010

4 commits

  • 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
     
  • 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
     
  • The MAX8998 chip have regulator and rtc features. The i2c slave address
    of regulator and rtc is different, so needs each i2c client on i2c
    operation functions.

    Also, this patch exports i2c operation functions instead of callback to
    make easy to read.

    Signed-off-by: Joonyoung Shim
    Signed-off-by: Kyungmin Park
    Signed-off-by: Samuel Ortiz

    Joonyoung Shim
     

01 Sep, 2010

3 commits


11 Aug, 2010

3 commits

  • In max8998_list_voltage() and max8998_set_voltage(),
    we use ldo as array index of ldo_voltage_map.
    Thus the valid range should be 0 .. ARRAY_SIZE(ldo_voltage_map)-1.

    Signed-off-by: Axel Lin
    Acked-by: Kyungmin Park
    Acked-by: Mark Brown
    Signed-off-by: Liam Girdwood

    Axel Lin
     
  • Two issues are addressed for max8998_set_voltage function.

    1. Min/Max Voltage.

    max8998_set_voltage had been using the voltage value of

    min ( voltage[i] >= max_vol , i )

    This is corrected to use:

    min ( voltage[i] >= min_vol , i )

    2. Ramp Up Delay.

    max8998_set_voltage should provide delay for BUCK1/2
    if ENRAMP is on. It reads RAMP value from ONOFF4 register to determine
    RAMP delay length. However, when max8998_set_voltage's new voltage is
    lower than the previous, we don't care because it does not deteriorate
    the stability.

    Changes since v1:
    - rebased onto latest regulator-for-next tree

    Signed-off-by: MyungJoo Ham
    Signed-off-by: Kyungmin Park
    Signed-off-by: Marek Szyprowski
    Acked-by: Mark Brown
    Signed-off-by: Liam Girdwood

    MyungJoo Ham
     
  • Acked-by: Mark Brown

    This patch adds voltage regulator driver for Maxim 8998 chip. This chip
    is used on Samsung Aquila and GONI boards and provides following
    functionalities:
    - 4 BUCK voltage converters, 17 LDO power regulators and 5 other power
    controllers
    - battery charger

    This patch adds basic driver for voltage regulators and MAX 8998 MFD core.

    Signed-off-by: Kyungmin Park
    Signed-off-by: Marek Szyprowski
    Acked-by: Samuel Ortiz
    Acked-by: Mark Brown
    Signed-off-by: Liam Girdwood

    Kyungmin Park