03 Dec, 2009
1 commit
-
The version that made it into mainline missed the initialisation of the
chip handle.Signed-off-by: Mark Brown
Signed-off-by: Liam Girdwood
16 Nov, 2009
3 commits
-
Don't dereference drvdata after it has been freed.
regards,
dan carpenterSigned-off-by: Dan Carpenter
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood -
If ret is unsigned, the checks for negative wm831x_reg_read() return values
are wrong. The error value should be transmitted to its caller, e.g.
wm831x_gp_ldo_get_status() which tests for a negative return value.Signed-off-by: Roel Kluin
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood -
Signed-off-by: Mark Brown
Signed-off-by: Liam Girdwood
22 Sep, 2009
34 commits
-
Signed-off-by: Roel Kluin
Signed-off-by: Haojian Zhuang
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood -
Signed-off-by: Wolfram Sang
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood -
Specifying 'default n' is superfluous.
Signed-off-by: Wolfram Sang
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood -
For val to be greater than 7 or less than 20 is logically always true.
Signed-off-by: Roel Kluin
Cc: Liam Girdwood
Cc: Mark Brown
Signed-off-by: Andrew Morton
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood -
…ACE_CONSUMER description
Signed-off-by: Michael Prokop <mika@grml.org>
Signed-off-by: Liam Girdwood <lrg@slimlogic.co.uk> -
This makes _regulator_enable() properly handle the case where
a regulator is already on when you try to enable it. Currently
it will erroneously handle positive return values as an error.Signed-off-by: Linus Walleij
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood -
Fixes the following errors on both tps650xx regulator drivers :-
drivers/regulator/tps65023-regulator: struct i2c_device_id is 32 bytes. The last of 1 is:
0x74 0x70 0x73 0x36 0x35 0x30 0x32 0x33 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
FATAL: drivers/regulator/tps65023-regulator: struct i2c_device_id is not terminated with a NULL entry!This patch also fixes the GPL v2 licence string for both drivers.
Signed-off-by: Liam Girdwood
-
Adding TPS65023 and TPS6507x regulator driver support in
drivers/regulator/Makefile and drivers/regulator/KconfigSigned-off-by: Anuj Aggarwal
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood -
Adding support for TI TPS6507x regulator driver
Signed-off-by: Anuj Aggarwal
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood -
Adding support for TI TPS65023 regulator driver
Signed-off-by: Anuj Aggarwal
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood -
and avoid introducing our own loops for creating
several sysfs entries.Signed-off-by: Felipe Balbi
Acked-by: Mark Brown
Acked-by: Mike Rapoport
Signed-off-by: Liam Girdwood -
Now fixed regulators that have their enable pin connected to a GPIO line
can use the fixed regulator driver for regulator enable/disable control.
The GPIO number and polarity information is passed through platform data.
GPIO enable control is achieved using gpiolib.Signed-off-by: Roger Quadros
Reviewed-by: Philipp Zabel
Reviewed-by: Felipe Balbi
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood -
This patch implements list_voltage for the pcf50644 regulator driver.
As the voltages are linearly scaled the code to convert register values to
voltages can be reused and most of the code can be shared with get_voltage.Signed-off-by: Lars-Peter Clausen
Signed-off-by: Liam Girdwood -
The regulator_enable() code wasn't actually checking that the
machine constraints had given permission to enable the regulator.
Add code to do that, but only if the regulator is not already on
due to something like always_on or being left on at startup since
in those cases there's no physical change being introduced and the
constraint wouldn't make any sense.Also add matching code for disable(). We need to do less there since
either regulator_enable() should have succeeded first or the board
setup makes no sense.Signed-off-by: Mark Brown
Signed-off-by: Liam Girdwood -
Allows use by more of the internal regulator API code.
Signed-off-by: Mark Brown
Signed-off-by: Liam Girdwood -
Signed-off-by: Mark Brown
Signed-off-by: Liam Girdwood -
Signed-off-by: Mark Brown
Signed-off-by: Liam Girdwood -
Signed-off-by: Mark Brown
Signed-off-by: Liam Girdwood -
Signed-off-by: Mike Rapoport
Signed-off-by: Liam Girdwood -
Report errors to the user and try harder to clean up if we're not
able to probe.Signed-off-by: Mark Brown
Signed-off-by: Liam Girdwood -
The patch to add support for looking up consumers by device name
had the side effect of causing us to require a device which is
at best premature since at least cpufreq still operates outside
the device model. Remove that requirement.Reported-by: Haojian Zhuang
Signed-off-by: Mark Brown
Signed-off-by: Liam Girdwood -
We're probably going to start oopsing fairly soon after this happens.
Signed-off-by: Mark Brown
Signed-off-by: Liam Girdwood -
Simplify checking of support for voltage ranges by providing an API which
wraps the existing count and list operations.Signed-off-by: Mark Brown
Signed-off-by: Liam Girdwood -
Some consumers require complete control of the regulator and can't
tolerate sharing it with other consumers, most commonly because they need
to have the regulator actually disabled so can't have other consumers
forcing it on. This new regulator_get_exclusive() API call allows these
consumers to explicitly request this, documenting the assumptions that
they are making.In order to simplify coding of such consumers the use count for regulators
they request is forced to match the enabled state of the regulator when
it is requested. This is not possible for consumers which can share
regulators due to the need to keep track of the ownership of use counts.A new API call is used rather than an additional argument to the existing
regulator_get() in order to avoid merge headaches with driver code in
other trees.Signed-off-by: Mark Brown
Signed-off-by: Liam Girdwood -
Make da903x driver to list voltage and count voltage.
Signed-off-by: Haojian Zhuang
Acked-by: Mark Brown
Acked-by: Eric Miao
Signed-off-by: Liam Girdwood -
In PXA3xx SoC family, V_CORE power doamin is supplied by BUCK1 that is
controller by ADTV1 or ADTV2 register.By default, v1 and v2 has the same copy. If v1 or v2 is updated, the last
value that is written to either register takes effect. It means that v1
and v2 has different copy. And the actual voltage output is determinated
by last update on either register.DA9034/35 is binded with PXA3xx SoC family. While SoC is scaling OP or
entering/exiting lower power mode, SoC needs to change voltage of V_CORE
power doamin. In order to be efficient, POWER I2C (hardcode) mode could
be enabled in SoC. In this mode, SoC will control v2 register directly.In original DA903x driver, software will only read regulator data from v1
register. But SoC controls v2 register directly. It results that v1 and v2
isn't synchronized. Wrong data will be read from v1 register. So access v2
register in da903x driver instead.Signed-off-by: Haojian Zhuang
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood -
Support the operation of DA9030 BUCK2 in da903x driver.
Signed-off-by: Haojian Zhuang
Acked-by: Mark Brown
Acked-by: Eric Miao
Acked-by: Mike Rapoport
Signed-off-by: Liam Girdwood -
BUCK3 is the new component in DA9035. So there're three BUCKs in DA9035.
And there're two BUCKs in DA9034.Signed-off-by: Haojian Zhuang
Acked-by: Mark Brown
Acked-by: Eric Miao
Signed-off-by: Liam Girdwood -
Signed-off-by: Joe Perches
Signed-off-by: Liam Girdwood -
Follow the approach suggested by Russell King and implemented by him in
the clkdev API and allow consumer device supply mapings to be set up
using the dev_name() for the consumer instead of the struct device.
In order to avoid making existing machines instabuggy and creating merge
issues the use of struct device is still supported for the time being.This resolves problems working with buses such as I2C which make the
struct device available late providing that the final device name is
known, which is the case for most embedded systems with fixed setups.Consumers must still use the struct device when calling regulator_get().
Signed-off-by: Mark Brown
Signed-off-by: Liam Girdwood -
This makes it easier to read the logs when doing testing.
Signed-off-by: Mark Brown
Signed-off-by: Liam Girdwood -
Signed-off-by: Mark Brown
Signed-off-by: Liam Girdwood -
The core will no longer complain so we should log an error here.
Signed-off-by: Mark Brown
Signed-off-by: Liam Girdwood -
Ensure that reg is within the bounds of array wm8350->pmic.pdev[].
Signed-off-by: Roel Kluin
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood
17 Sep, 2009
2 commits
-
This sets the number of voltages for the AB3100 regulators so that
they play well with the voltage listing functions and can be used
properly with the MMC regulator integration glue for example.Signed-off-by: Linus Walleij
Signed-off-by: Samuel Ortiz -
This adds support for the regulators found in the AB3100
Mixed-Signal IC.It further also defines platform data for the ST-Ericsson
U300 platform and extends the AB3100 MFD driver so that
platform/board data with regulation constraints and an init
function can be passed down all the way from the board to
the regulators.Signed-off-by: Linus Walleij
Acked-by: Mark Brown
Signed-off-by: Liam Girdwood
Signed-off-by: Samuel Ortiz