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
     

01 Nov, 2011

1 commit


09 Jul, 2011

3 commits

  • The ramp_delay variable can be set lower than the desired value.
    This patch fixes it.

    Signed-off-by: Donggeun Kim
    Signed-off-by: MyungJoo Ham
    Signed-off-by: KyungMin Park
    Acked-by: Mark Brown
    Signed-off-by: Liam Girdwood

    Donggeun Kim
     
  • The platform_data (pdata) may be pointing to __initdata section, which
    may be free'd from the memory. The dependency on pdata in non-init
    functions is removed in this patch to allow platform to declare
    __initdata for platform data.

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

    MyungJoo Ham
     
  • Currently, ramp_delay variable is used uninitialzed in
    max8997_set_voltage_ldobuck which gets called through
    regulator_register calls.

    To fix the problem, in max8997_pmic_probe, ramp_delay initialization
    code is moved before calls to regulator_register.

    Cc: Liam Girdwood
    Cc: Mark Brown
    Cc: MyungJoo Ham
    Cc: Kyungmin Park
    Cc: Samuel Ortiz
    Signed-off-by: Tushar Behera
    Acked-by: MyungJoo Ham
    Acked-by: Mark Brown
    Signed-off-by: Liam Girdwood

    Tushar Behera
     

27 May, 2011

2 commits

  • In current implementation, the original macro implementation assumes the caller
    pass the parameter starting from 1 (to match the register names in datasheet).
    Thus we have unneeded plus one then minus one operations
    when using MAX8997_REG_BUCK1DVS/MAX8997_REG_BUCK2DVS/MAX8997_REG_BUCK5DVS macros.

    This patch removes these macros to avoid unneeded plus one then minus one operations
    without reducing readability.

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

    Axel Lin
     
  • fix unreachable code.

    Signed-off-by: Jonghwan Choi
    Signed-off-by: MyungJoo Ham
    Acked-by: Mark Brown
    Signed-off-by: Liam Girdwood

    Jonghwan Choi
     

27 Mar, 2011

1 commit


23 Mar, 2011

1 commit

  • This patch supports PMIC/Regulator part of MAX8997/MAX8966 MFD.
    In this initial release, selecting voltages or current-limit
    and switching on/off the regulators are supported.

    Controlling voltages for DVS with GPIOs is not implemented fully
    and requires more considerations: it controls multiple bucks (selection
    of 1, 2, and 5) at the same time with SET1~3 gpios. Thus, when DVS-GPIO
    is activated, we lose the ability to control the voltage of a single
    buck regulator independently; i.e., contolling a buck affects other two
    bucks. Therefore, using the conventional regulator framework directly
    might be problematic. However, in this driver, we try to choose
    a setting without such side effect of affecting other regulators and
    then try to choose a setting with the minimum side effect (the sum of
    voltage changes in other regulators).

    On the other hand, controlling all the three bucks simultenously based
    on the voltage set table may help build cpufreq and similar system
    more robust; i.e., all the three voltages are consistent every time
    without glitches during transition.

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

    MyungJoo Ham