30 Jul, 2013
1 commit
-
Use the wrapper function for retrieving the platform data instead of
accessing dev->platform_data directly.Signed-off-by: Jingoo Han
Signed-off-by: Mark Brown
12 May, 2013
1 commit
-
Since 0998d06310 "device-core: Ensure drvdata = NULL when no driver is bound",
this is done by driver core after device_release or on probe failure.
Thus we can remove all platform_set_drvdata(pdev, NULL) in drivers.Signed-off-by: Axel Lin
Signed-off-by: Mark Brown
04 Mar, 2013
1 commit
-
The info parameter is not used at all, remove it.
Signed-off-by: Axel Lin
Acked-by: Haojian Zhuang
Signed-off-by: Mark Brown
30 Jan, 2013
1 commit
-
of_find_node_by_name() returns a node pointer with refcount incremented, use
of_node_put() on it when done.of_find_node_by_name() will call of_node_put() against from parameter,
thus we also need to call of_node_get(from) before calling
of_find_node_by_name().Signed-off-by: Axel Lin
Signed-off-by: Mark Brown
20 Nov, 2012
3 commits
-
CONFIG_HOTPLUG is going away as an option so __devexit is no
longer needed.Signed-off-by: Bill Pemberton
Signed-off-by: Mark Brown -
CONFIG_HOTPLUG is going away as an option so __devinit is no longer
needed.Signed-off-by: Bill Pemberton
Signed-off-by: Mark Brown -
CONFIG_HOTPLUG is going away as an option so __devexit_p is no longer
needed.Signed-off-by: Bill Pemberton
Signed-off-by: Mark Brown
07 Nov, 2012
1 commit
-
Signed-off-by: Qing Xu
Signed-off-by: Mark Brown
19 Sep, 2012
1 commit
-
Remove array in parent's platform data. Use struct regulator_init_data
as regulator device's platform data directly. So a lot of pdata are
added into parent's platform data. And voltage out register offset
is used as IORESOURCE_REG to distinguish different regualtor devices.Signed-off-by: Haojian Zhuang
Signed-off-by: Samuel Ortiz
18 May, 2012
1 commit
-
This driver has been converted to use regulator_map_voltage_linear and
set_voltage_sel now. regulator_map_voltage_linear will check the the voltage
falls within specified range. The check_range() function and max_uV field are
not used now, remove them.Signed-off-by: Axel Lin
Signed-off-by: Mark Brown
14 May, 2012
3 commits
-
Signed-off-by: Axel Lin
Signed-off-by: Mark Brown -
Signed-off-by: Axel Lin
Signed-off-by: Mark Brown -
Signed-off-by: Axel Lin
Signed-off-by: Mark Brown
09 Apr, 2012
1 commit
-
Rather than adding new arguments to regulator_register() every time we
want to add a new bit of dynamic information at runtime change the function
to take these via a struct. By doing this we avoid needing to do further
changes like the recent addition of device tree support which required each
regulator driver to be updated to take an additional parameter.The regulator_desc which should (mostly) be static data is still passed
separately as most drivers are able to configure this statically at build
time.Signed-off-by: Mark Brown
03 Apr, 2012
2 commits
-
The n_voltages are the same for all regulators: (max - min / step) + 1 == 64.
The vol_shift is always 0, and the vol_nbits is always the same as n_voltages
setting. Thus we can remove vol_shitf and vol_nbits fields from struct
max8925_regulator_info.Signed-off-by: Axel Lin
Signed-off-by: Mark Brown -
Current code implements max8925_list_voltage but does not set the list_voltage
callback function in max8925_regulator_[ldo|sdv]_ops. Fix it.Signed-off-by: Axel Lin
Signed-off-by: Mark Brown
14 Mar, 2012
1 commit
-
Use DIV_ROUND_UP macro for better readability.
Signed-off-by: Axel Lin
Signed-off-by: Mark Brown
07 Jan, 2012
1 commit
-
Max8925 ldo status should be determined by two factors:
1. power up/down sequence selection(LDOCTL[4:2]).
2. i2c enable bit(LDOCTL[0]).Max8925 ldo support two types of power up/down sequence:
1. flexible sequence(LDOCTL[4:2] = 0~6).
2. i2c sequence(LDOCTL[4:2] = 7).With flexible sequence selected, the ldo is enabled during power up by default.
With i2c sequence selected, the ldo is controlled by the i2c enable bit(LDOCTL[0]).Signed-off-by: Kevin Liu
Signed-off-by: Haojian Zhuang
Signed-off-by: Mark Brown
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
01 Nov, 2011
1 commit
-
Another group of drivers that are taking advantage of the implicit
presence of module.h -- and will break when we pull the carpet out
from under them during a cleanup. Fix 'em now.Signed-off-by: Paul Gortmaker
27 May, 2011
1 commit
-
Force to enable i2c as power up/down sequence. Otherwise, SD/LDO can't
be enabled or disabled via accessing i2c bus.Signed-off-by: Haojian Zhuang
Cc: Liam Girdwood
Acked-by: Mark Brown
Signed-off-by: Samuel Ortiz
12 Jan, 2011
1 commit
-
Change the interface used by set_voltage() to report the selected value
to the regulator core in terms of a selector used by list_voltage().
This allows the regulator core to know the voltage that was chosen
without having to do an explict get_voltage(), which would be much more
expensive as it will generally access hardware.Signed-off-by: Mark Brown
Signed-off-by: Liam Girdwood
28 Apr, 2010
1 commit
-
Fix regulator enabling issue that is caused by typo error in is_enabled().
Signed-off-by: Haojian Zhuang
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood
23 Mar, 2010
1 commit
-
It is a good tone to reset driver data after unbinding the device.
Also change find_regulator_info() fro inline to __devinit - let compiler
figure out if it wants it to be inlined or not.Signed-off-by: Dmitry Torokhov
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood
08 Mar, 2010
1 commit
-
MAX8925 contains 3 Buck and 20 LDO regulator.
Signed-off-by: Haojian Zhuang
Acked-by: Mark Brown
Signed-off-by: Samuel Ortiz