linux.git/drivers/power/supply, branch v4.9

power: supply: bq27xxx_battery: allow kernel poll_interval parameter runtime update

2016-09-21T00:08:04+00:00

Fix issue with poll_interval being not updated till the previous
interval expired.

Cc: Tony Lindgren 
Cc: Liam Breck 
Signed-off-by: Matt Ranostay 
Signed-off-by: Sebastian Reichel

power: supply: sbs-battery: Cleanup removal of chip->pdata

2016-09-21T00:04:47+00:00

There where still a few lingering references to pdata after commit
power: supply: sbs-battery: simplify DT parsing.

Remove pdata from struct·sbs_info and conditional checks to ser if this
was set from the i2c read / write functions.
Instead of call max in each function for incrementing poll_retry_count
do it once in the probe function.
Fixup null pointer dereference in to pdata in sbs_external_power_changed.
Change retry counts to u32 to avoid need for max.

Signed-off-by: Phil Reid 
Signed-off-by: Sebastian Reichel

power: supply: ab8500: cleanup with list_first_entry_or_null()

2016-09-19T19:22:10+00:00

The combo of list_empty() check and return list_first_entry()
can be replaced with list_first_entry_or_null().

Signed-off-by: Masahiro Yamada 
Signed-off-by: Sebastian Reichel

sbs-battery: make writes to ManufacturerAccess optional

2016-09-19T19:02:17+00:00

According to the Smart Battery Data Specification, the use
of ManufacturerAcess (register 0x0) is implementation-defined.
It appears that some batteries use writes to this register
in order to implement certain functionality, but others may
simply NAK all writes to it. As a result, write failures to
ManufacturerAccess should not be used as an indicator of
battery presence, nor as a failure to enter sleep mode.

The failed write access was seen with SANYO AP13J3K.

Cc: Brian Norris 
Signed-off-by: Guenter Roeck 
Signed-off-by: Sebastian Reichel

power: bq24257: Fix use of uninitialized pointer bq->charger

2016-09-19T18:56:22+00:00

bq->charger is initialized in bq24257_power_supply_init.
Therefore, bq24257_power_supply_init should be called before the
registration of the IRQ handler bq24257_irq_handler_thread that calls
power_supply_changed(bq->charger).

Signed-off-by: Georges Savoundararadj 
Cc: Aurelien Chanot 
Cc: Andreas Dannenberg 
Cc: Sebastian Reichel 
Cc: David Woodhouse 
Fixes: 2219a935963e ("power_supply: Add TI BQ24257 charger driver")
Signed-off-by: Sebastian Reichel

power: supply: sbs-battery: simplify DT parsing

2016-09-06T23:46:59+00:00

After the change to use the gpio descriptor interface, we get a warning if
-Wmaybe-uninitialized is added back to the build flags (it is currently
disabled:

drivers/power/supply/sbs-battery.c: In function 'sbs_probe':
drivers/power/supply/sbs-battery.c:760:28: error: 'pdata' may be used uninitialized in this function [-Werror=maybe-uninitialized]

The problem is that if neither the DT properties nor a platform_data
pointer are provided, the chip->pdata pointer gets set to an uninitialized
value.

Looking at the code some more, I found that the sbs_of_populate_pdata
function is more complex than necessary and has confusing calling
conventions of possibly returning a valid pointer, a NULL pointer
or an ERR_PTR pointer (in addition to the uninitialized pointer).

To fix all of that, this gets rid of the chip->pdata pointer and
simply moves the two integers into the sbs_info structure. This
makes it much clearer from reading sbs_probe() what the precedence
of the three possible values are (pdata, DT, hardcoded defaults)
and completely avoids the #ifdef CONFIG_OF guards as
of_property_read_u32() gets replaced with a compile-time stub
when that is disabled, and returns an error if passed a NULL of_node
pointer.

Signed-off-by: Arnd Bergmann 
Fixes: 3b5dd3a49496 ("power: supply: sbs-battery: Use gpio_desc and sleeping calls for battery detect")
Signed-off-by: Sebastian Reichel

power: supply: bq24735-charger: Request status GPIO with initial input setup

2016-09-05T10:59:49+00:00

This requests the status GPIO with initial input setup. It is required
to read the GPIO status at probe time and thus correctly avoid sending
I2C messages when AC is not plugged.

When requesting the GPIO without initial input setup, it always reads 0
which causes probe to fail as it assumes the charger is connected, sends
I2C messages and fails.

While at it, this switches the driver over to gpiod API.

Signed-off-by: Paul Kocialkowski 
Signed-off-by: Sebastian Reichel

power: supply: sbs-battery: Use gpio_desc and sleeping calls for battery detect

2016-09-01T14:06:14+00:00

Switch to using new gpio_desc interface and devm gpio get calls to
automatically manage gpio resource. Use gpiod_get_value which handles
active high / low calls.

If gpio_detect is set then force loading of the driver as it is
reasonable to assume that the battery may not be present.

Update the is_present flag immediately in the IRQ.

Remove legacy gpio specification from platform data.

Signed-off-by: Phil Reid 
Signed-off-by: Sebastian Reichel

power: supply: act8945a_charger: Add max current property

2016-09-01T11:55:55+00:00

Add the power supply's current max property,
POWER_SUPPLY_PROP_CURRENT_MAX.

Signed-off-by: Wenyou Yang 
Signed-off-by: Sebastian Reichel

power: supply: act8945a_charger: Add capacity level property

2016-09-01T11:55:52+00:00

Add the power supply capacity level property, it corresponds to
POWER_SUPPLY_CAPACITY_LEVEL_*.

It also utilizes the precision voltage detector function module
to catch the low battery voltage.

Signed-off-by: Wenyou Yang 
Signed-off-by: Sebastian Reichel