linux-toradex.git/drivers/regulator/max8998.c, branch v3.4.2

regulator: Silence error message in max8998_pmic_probe

2012-03-11T20:48:54+00:00

This looks like a mistakenly committed debug logging.

Signed-off-by: Axel Lin 
Signed-off-by: Mark Brown

regulator: Kill max8998_get_ldo function

2012-03-11T20:48:47+00:00

Use rdev_get_id() directly.

Signed-off-by: Axel Lin 
Signed-off-by: Mark Brown

regulator: pass additional of_node to regulator_register()

2011-11-23T18:47:04+00:00

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

regulator: Fix memory leak in max8998_pmic_probe failure path

2011-05-27T09:49:09+00:00

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

treewide: cleanup continuations and remove logging message whitespace

2011-04-26T08:24:37+00:00

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

regulator: Add MODULE_DEVICE_TABLE to max8997 and max8998

2011-03-27T10:47:25+00:00

The device table is required to load modules based on modaliases.

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

regulator: Support MAX8998/LP3974 DVS-GPIO

2011-01-14T11:38:16+00:00

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

mfd: Support LP3974 RTC

2011-01-14T11:38:16+00:00

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

regulator: Fix prototype for MAX8998 buck set_voltage()

2011-01-12T14:33:01+00:00

Signed-off-by: Mark Brown 
Signed-off-by: Liam Girdwood

regulator: Report actual configured voltage to set_voltage()

2011-01-12T14:32:59+00:00

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