linux-toradex.git/drivers/regulator, branch v2.6.35-rc2

i2c: Remove all i2c_set_clientdata(client, NULL) in drivers

2010-06-03T09:33:58+00:00

I2C drivers can use the clientdata-pointer to point to private data. As I2C
devices are not really unregistered, but merely detached from their driver, it
used to be the drivers obligation to clear this pointer during remove() or a
failed probe(). As a couple of drivers forgot to do this, it was agreed that it
was cleaner if the i2c-core does this clearance when appropriate, as there is
no guarantee for the lifetime of the clientdata-pointer after remove() anyhow.
This feature was added to the core with commit
e4a7b9b04de15f6b63da5ccdd373ffa3057a3681 to fix the faulty drivers.

As there is no need anymore to clear the clientdata-pointer, remove all current
occurrences in the drivers to simplify the code and prevent confusion.

Signed-off-by: Wolfram Sang 
Acked-by: Mark Brown 
Acked-by: Greg Kroah-Hartman 
Acked-by: Richard Purdie 
Acked-by: Dmitry Torokhov 
Signed-off-by: Jean Delvare

mfd: AB3100 register access change to abx500 API

2010-05-27T23:37:45+00:00

The interface for the AB3100 is changed to make way for the
ABX500 family of chips: AB3550, AB5500 and future ST-Ericsson
Analog Baseband chips. The register access functions are moved
out to a separate struct abx500_ops. In this way the interface
is moved from the implementation and the sub functionality drivers
can keep their interface intact when chip infrastructure and
communication mechanisms changes. We also define the AB3550
device IDs and the AB3550 platform data struct and convert
the catenated 32bit event to an array of 3 x 8bits.

Signed-off-by: Mattias Wallin 
Signed-off-by: Linus Walleij 
Signed-off-by: Samuel Ortiz

mfd: Renamed ab3100.h to abx500.h

2010-05-27T23:37:44+00:00

The goal here is to make way for a more general interface for the
analog baseband chips ab3100 ab3550 ab550 and future chips.

This patch have been divided into two parts since both changing name
and content of a file is not recommended in git.

Signed-off-by: Mattias Wallin 
Signed-off-by: Linus Walleij 
Signed-off-by: Samuel Ortiz

mfd: Add TPS6507x support

2010-05-27T23:37:38+00:00

TPS6507x are multi function (PM, touchscreen) chipsets from TI.
This commit also changes the corresponding regulator driver from being
standalone to an MFD subdevice.

Signed-off-by: Todd Fischer 
Acked-by: Mark Brown 
Signed-off-by: Liam Girdwood 
Signed-off-by: Samuel Ortiz

regulator: tps6057x namespace cleanup

2010-05-27T23:37:37+00:00

Move from using tps or tsp6507x to tps6057x_pmic in a consistent manner.

Signed-off-by: Todd Fischer 
Acked-by: Mark Brown 
Signed-off-by: Liam Girdwood 
Signed-off-by: Samuel Ortiz

mfd: Add tps6507x board data structure

2010-05-27T23:37:37+00:00

Add mfd structure which refrences sub-driver initialization data. For example,
for a giving hardware implementation, the voltage regulator sub-driver
initialization data provides the mapping betten a voltage regulator and what
the output voltage is being used for.

Signed-off-by: Todd Fischer 
Acked-by: Mark Brown 
Signed-off-by: Liam Girdwood 
Signed-off-by: Samuel Ortiz

mfd: Move TPS6507x register definition to header file.

2010-05-27T23:37:36+00:00

Other sub-drivers for the TPS6507x chip will need to use register
definition so move it out of the source file and into a header file.

Signed-off-by: Todd Fischer 
Acked-by: Mark Brown 
Signed-off-by: Liam Girdwood 
Signed-off-by: Samuel Ortiz

regulator: return set_mode is same mode is requested

2010-05-25T09:16:02+00:00

On Mon, 2010-05-17 at 17:34 +0200, Mark Brown wrote:
> This doesn't seem like the right error handling - if the driver has a
> set_mode() you'd *expect* it to have a get_mode() but there's no need
> for it to be a strict requirement.
True. In such a case, even a valid request would be lost! So now
in the updated patch:
 - check if get_mode is present to avoid oops;
 - if get_mode is not present, proceed anyways for the request.

Here is the updated patch:

>From bad0d5eb51ef84be5b100e3dd0f5a590ea0529b6 Mon Sep 17 00:00:00 2001
From: Sundar R Iyer 
Date: Fri, 14 May 2010 15:14:17 +0530
Subject: [PATCH 1/1] regulator: return set_mode when same mode is requested

save I/O costs by returning when the same mode is
requested for the regulator

Cc: Liam Girdwood 
Cc: Mark Brown 
Acked-by: Linus Walleij 
Signed-off-by: Sundar R Iyer 
Acked-by: Mark Brown 
Signed-off-by: Liam Girdwood

Regulators: ab3100/bq24022: add a missing .owner field in regulator_desc

2010-05-25T09:16:02+00:00

This patch adds a missing .owner field in regulator_desc, which is used for refcounting.

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

twl6030: regulator: Remove vsel tables and use formula for calculation

2010-05-25T09:16:02+00:00

All twl6030 regulators can be programmed from 1.0v to 3.3v
with 100mV steps.
The below formula can be used to calculate the vsel values
to be programmed in the VREG_VOLTAGE registers.

Voltage(in mV) = 1000mv + 100mv * (vsel - 1)

Ex: if vsel = 0x9, mV = 1000 + 100 * (9 -1) = 1800mV.

This patch removes all existing VSEL tables for twl6030 adjustable
regulators and just uses the formula directly for vsel calculations
after verifing they fall in the allowed range.

Signed-off-by: Rajendra Nayak 
Cc: Liam Girdwood 
Cc: Samuel Ortiz 
Cc: Mark Brown 
Acked-by: Mark Brown 
Signed-off-by: Liam Girdwood