14 Jan, 2012
1 commit
-
* 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/sameo/mfd-2.6: (59 commits)
rtc: max8925: Add function to work as wakeup source
mfd: Add pm ops to max8925
mfd: Convert aat2870 to dev_pm_ops
mfd: Still check other interrupts if we get a wm831x touchscreen IRQ
mfd: Introduce missing kfree in 88pm860x probe routine
mfd: Add S5M series configuration
mfd: Add s5m series irq driver
mfd: Add S5M core driver
mfd: Improve mc13xxx dt binding document
mfd: Fix stmpe section mismatch
mfd: Fix stmpe build warning
mfd: Fix STMPE I2c build failure
mfd: Constify aat2870-core i2c_device_id table
gpio: Add support for stmpe variant 801
mfd: Add support for stmpe variant 801
mfd: Add support for stmpe variant 610
mfd: Add support for STMPE SPI interface
mfd: Separate out STMPE controller and interface specific code
misc: Remove max8997-muic sysfs attributes
mfd: Remove unused wm831x_irq_data_to_mask_reg()
...Fix up trivial conflict in drivers/leds/Kconfig due to addition of
LEDS_MAX8997 and LEDS_TCA6507 next to each other.
09 Jan, 2012
1 commit
-
This moves all the header files related to the abx500 family into
a common include directory below mfd. From now on we place any
subchip header in that directory. Headers previously in e.g.
get prefixed and are now e.g.
. The top-level abstract interface
remains in .Signed-off-by: Linus Walleij
Signed-off-by: Samuel Ortiz
07 Jan, 2012
2 commits
-
Fix fixed regulator using DT failed to call regulator_register.
of_get_regulator_init_data set apply_uV to 1, but fixed regulator
doesn't need it. Set it back to 0.Signed-off-by: Richard Zhao
Signed-off-by: Mark Brown -
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
04 Jan, 2012
1 commit
-
This patch allows consumers to forcibly disable multiple regulator
clients in a single API call.Signed-off-by: Donggeun Kim
Signed-off-by: MyungJoo Ham
Signed-off-by: Kyungmin Park
Signed-off-by: Mark Brown
02 Jan, 2012
2 commits
-
regulator_get needs of_node to find right regulator.
Signed-off-by: Richard Zhao
Signed-off-by: Mark Brown -
During regulator_register, the rail is set on the provided
machine constraints and if it is enabled then it is also
require to enable the supply regulator. This will make sure
that:
1. Proper reference count for supply regulator to be maintain.
2. Supply regulator should be enable when given rail is enabled.Signed-off-by: Laxman Dewangan
Signed-off-by: Mark Brown
30 Dec, 2011
2 commits
-
Convert mc13892-regulator driver to use devm_kzalloc().
Signed-off-by: Fabio Estevam
Signed-off-by: Mark Brown -
Convert mc13783-regulator driver to use devm_kzalloc().
Signed-off-by: Fabio Estevam
Signed-off-by: Mark Brown
29 Dec, 2011
3 commits
-
create_regulator() returns NULL on fail.
Signed-off-by: Axel Lin
Signed-off-by: Mark Brown -
In the case of create_regulator() fails, goto the error path immediately.
It does not make sense to update rdev->open_count if create_regulator fails.Signed-off-by: Axel Lin
Signed-off-by: Mark Brown -
It's part of the driver interface so should be available to modules.
Signed-off-by: Mark Brown
22 Dec, 2011
2 commits
-
It adds device tree probe support for mc13892-regulator driver.
Signed-off-by: Shawn Guo
Signed-off-by: Mark Brown -
It's not really necessary to add a prefix 'MC13892__' for each mc13892
regulator name, since the chip must have been identified as mc13892
when we look at the regulator name.Signed-off-by: Shawn Guo
Signed-off-by: Mark Brown
20 Dec, 2011
2 commits
-
Signed-off-by: Mark Brown
-
da9052_regulator_info and da9053_regulator_info are not used outside
this driver so no need to make the symbol global.Signed-off-by: Axel Lin
Signed-off-by: Mark Brown
17 Dec, 2011
1 commit
-
Reported-by: Mark Brown
Signed-off-by: David Dajun Chen
Signed-off-by: Ashish Jangam
Signed-off-by: Mark Brown
15 Dec, 2011
2 commits
-
Reported-by: Stephen Rothwell
Signed-off-by: Mark Brown -
The Dialog PMIC has below featured regulators:-
DA9052-BC - 4 DVS Buck converters 0.5V - 3.6V upto 1Amp.
DA9053-AA/BX - 4 DVS Buck converters 0.5V - 2.5V upto 3Amp.
DA9052/53 - 10 Programmable LDO's High PSSR, 1% accuracy.This patch support all the DA9052 and Da9053 regulators. The output voltages are
fully programmable via I2C or SPI interface. The platform data with regulation
constraints is passed down from the board to the regulator.Signed-off-by: David Dajun Chen
Signed-off-by: Ashish Jangam
Tested-by: Ying-Chun Liu (PaulLiu)
Signed-off-by: Mark Brown
06 Dec, 2011
3 commits
-
…/regulator into regulator-next
-
It's not always true that the device_node of regulator can be found
at dev->of_node at the time when of_get_regulator_init_data() is being
called, because in some cases the regulator nodes in device tree do
not have 'struct device' behind them until regulator_dev gets created
for it by core function regulator_register().The patch adds device_node as a new parameter to
of_get_regulator_init_data(), so that caller can pass in the node of
regulator directly.Signed-off-by: Shawn Guo
Cc: Mark Brown
Cc: Liam Girdwood
Signed-off-by: Mark Brown -
Otherwise there is no way in the bindings to configure a fixed voltage
via software. It seems reasonable to assume that if the binding explicitly
specifies a voltage we want to actually use that voltage.Signed-off-by: Mark Brown
30 Nov, 2011
1 commit
-
This allows read-only access to the device configuration which may be
useful for diagnostics.Signed-off-by: Mark Brown
Acked-by: Liam Girdwood
29 Nov, 2011
2 commits
-
SMPS regulator voltage control differs from the one of the LDO ones.
Current TWL code was using LDO regulator ops for controlling the SMPS
regulators, which fails. This was fixed fixed by adding separate
regulator type which uses correct logic and calculations for the
voltage levels.Signed-off-by: Tero Kristo
Signed-off-by: Mark Brown
Cc: stable@kernel.org
28 Nov, 2011
8 commits
-
This is caused by dereferencing 'rdev' after device_unregister() in
the regulator_unregister() function. 'rdev' is freed by
device_unregister(), so it must not be dereferenced after this call.[Edited commit message for legibility -- broonie]
Signed-off-by: Lothar Waßmann
Signed-off-by: Mark Brown -
This patch converts virtual and userspace regulator consumer drivers to use the
module_platform_driver() macro which makes the code smaller and a bit simpler.Signed-off-by: Axel Lin
Signed-off-by: Mark Brown -
The implementation in aat2870_update() already did the bitwise and operation
against mask parameter.Signed-off-by: Axel Lin
Signed-off-by: Mark Brown -
In current implementation, the pointer ri is not NULL if no id is matched.
Fix it by checking i == ARRAY_SIZE(aat2870_regulators) if no id is matched.Signed-off-by: Axel Lin
Signed-off-by: Mark Brown
Cc: stable@kernel.org -
of_get_fixed_voltage_config() may return NULL, return -ENOMEM in this case
so we don't dereference NULL pointer.Signed-off-by: Axel Lin
Signed-off-by: Mark Brown
27 Nov, 2011
4 commits
-
It is not used outside this driver so no need to make the symbol global.
Signed-off-by: Axel Lin
Signed-off-by: Mark Brown -
of_get_regulator_init_data() may return NULL, thus
check the return value to avoid NULL pointer dereference.Signed-off-by: Axel Lin
Signed-off-by: Mark Brown -
of_get_regulator_init_data is called in drivers/regulator/fixed.c
which could be a module.Export of_get_regulator_init_data to fix below build error:
ERROR: "of_get_regulator_init_data" [drivers/regulator/fixed.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2Reported-by: Randy Dunlap
Signed-off-by: Axel Lin
Signed-off-by: Mark Brown
24 Nov, 2011
3 commits
-
The commit 2c043bcbf287 ("regulator: pass additional of_node to
regulator_register()") caused a compile break because it missed
updating the regulator_register() call in gpio-regulator.c with
the additional parameter (NULL).The compile break as reported by Stephen Rothwell with the
x86_64 allmodconfig looked like thisdrivers/regulator/gpio-regulator.c: In function 'gpio_regulator_probe':
drivers/regulator/gpio-regulator.c:287:8: error: too few arguments to function 'regulator_register'
include/linux/regulator/driver.h:215:23: note: declared hereReported-by: Stephen Rothwell
Signed-off-by: Rajendra Nayak
Signed-off-by: Mark Brown
