linux-stable.git/drivers/power, branch v4.9.232

power: supply: smb347-charger: IRQSTAT_D is volatile

2020-06-30T19:38:24+00:00

[ Upstream commit c32ea07a30630ace950e07ffe7a18bdcc25898e1 ]

Fix failure when USB cable is connected:
smb347 2-006a: reading IRQSTAT_D failed

Fixes: 1502cfe19bac ("smb347-charger: Fix battery status reporting logic for charger faults")

Tested-by: David Heidelberg 
Signed-off-by: Dmitry Osipenko 
Signed-off-by: David Heidelberg 
Signed-off-by: Sebastian Reichel 
Signed-off-by: Sasha Levin

power: supply: lp8788: Fix an error handling path in 'lp8788_charger_probe()'

2020-06-30T19:38:24+00:00

[ Upstream commit 934ed3847a4ebc75b655659c4d2349ba4337941c ]

In the probe function, in case of error, resources allocated in
'lp8788_setup_adc_channel()' must be released.

This can be achieved easily by using the devm_ variant of
'iio_channel_get()'.
This has the extra benefit to simplify the remove function and to axe the
'lp8788_release_adc_channel()' function which is now useless.

Fixes: 98a276649358 ("power_supply: Add new lp8788 charger driver")
Signed-off-by: Christophe JAILLET 
Signed-off-by: Sebastian Reichel 
Signed-off-by: Sasha Levin

power: supply: bq24257_charger: Replace depends on REGMAP_I2C with select

2020-06-30T19:38:20+00:00

[ Upstream commit 87c3d579c8ed0eaea6b1567d529a8daa85a2bc6c ]

regmap is a library function that gets selected by drivers that need
it. No driver modules should depend on it. Depending on REGMAP_I2C makes
this driver only build if another driver already selected REGMAP_I2C,
as the symbol can't be selected through the menu kernel configuration.

Fixes: 2219a935963e ("power_supply: Add TI BQ24257 charger driver")
Signed-off-by: Enric Balletbo i Serra 
Signed-off-by: Sebastian Reichel 
Signed-off-by: Sasha Levin

power: vexpress: add suppress_bind_attrs to true

2020-06-20T08:24:20+00:00

commit 73174acc9c75960af2daa7dcbdb9781fc0d135cb upstream.

Make sure that the POWER_RESET_VEXPRESS driver won't have bind/unbind
attributes available via the sysfs, so lets be explicit here and use
".suppress_bind_attrs = true" to prevent userspace from doing something
silly.

Link: https://lore.kernel.org/r/20200527112608.3886105-2-anders.roxell@linaro.org
Cc: stable@vger.kernel.org
Signed-off-by: Anders Roxell 
Signed-off-by: Arnd Bergmann 
Signed-off-by: Greg Kroah-Hartman

power: supply: bq27xxx_battery: Silence deferred-probe error

2020-04-24T05:59:11+00:00

[ Upstream commit 583b53ece0b0268c542a1eafadb62e3d4b0aab8c ]

The driver fails to probe with -EPROBE_DEFER if battery's power supply
(charger driver) isn't ready yet and this results in a bit noisy error
message in KMSG during kernel's boot up. Let's silence the harmless
error message.

Signed-off-by: Dmitry Osipenko 
Reviewed-by: Andrew F. Davis 
Reviewed-by: Pali Rohár 
Signed-off-by: Sebastian Reichel 
Signed-off-by: Sasha Levin

power: supply: ltc2941-battery-gauge: fix use-after-free

2020-02-14T21:31:01+00:00

commit a60ec78d306c6548d4adbc7918b587a723c555cc upstream.

This driver's remove path calls cancel_delayed_work().
However, that function does not wait until the work function
finishes. This could mean that the work function is still
running after the driver's remove function has finished,
which would result in a use-after-free.

Fix by calling cancel_delayed_work_sync(), which ensures that
that the work is properly cancelled, no longer running, and
unable to re-schedule itself.

This issue was detected with the help of Coccinelle.

Cc: stable 
Signed-off-by: Sven Van Asbroeck 
Signed-off-by: Sebastian Reichel 
Signed-off-by: Greg Kroah-Hartman

power: supply: Init device wakeup after device_add()

2020-01-29T09:24:31+00:00

[ Upstream commit 8288022284859acbcc3cf1a073a1e2692d6c2543 ]

We may want to use the device pointer in device_init_wakeup() with
functions that expect the device to already be added with device_add().
For example, if we were to link the device initializing wakeup to
something in sysfs such as a class for wakeups we'll run into an error.
It looks like this code was written with the assumption that the device
would be added before initializing wakeup due to the order of operations
in power_supply_unregister().

Let's change the order of operations so we don't run into problems here.

Fixes: 948dcf966228 ("power_supply: Prevent suspend until power supply events are processed")
Cc: Greg Kroah-Hartman 
Cc: Tri Vo 
Cc: Kalesh Singh 
Cc: Ravi Chandra Sadineni 
Cc: Viresh Kumar 
Signed-off-by: Stephen Boyd 
Acked-by: Rafael J. Wysocki 
Signed-off-by: Sebastian Reichel 
Signed-off-by: Sasha Levin

PM / AVS: SmartReflex: NULL check before some freeing functions is not needed

2019-12-05T14:34:17+00:00

[ Upstream commit 14d338a857f05f894ba3badd9e6d3039c68b8180 ]

NULL check before some freeing functions is not needed.

Signed-off-by: Thomas Meyer 
Reviewed-by: Kevin Hilman 
Signed-off-by: Rafael J. Wysocki 
Signed-off-by: Sasha Levin

power: supply: twl4030_charger: disable eoc interrupt on linear charge

2019-11-25T08:52:32+00:00

[ Upstream commit 079cdff3d0a09c5da10ae1be35def7a116776328 ]

This avoids getting woken up from suspend after power interruptions
when the bci wrongly thinks the battery is full just because
of input current going low because of low input power

Signed-off-by: Andreas Kemnade 
Signed-off-by: Sebastian Reichel 
Signed-off-by: Sasha Levin

power: supply: twl4030_charger: fix charging current out-of-bounds

2019-11-25T08:52:32+00:00

[ Upstream commit 8314c212f995bc0d06b54ad02ef0ab4089781540 ]

the charging current uses unsigned int variables, if we step back
if the current is still low, we would run into negative which
means setting the target to a huge value.
Better add checks here.

Signed-off-by: Andreas Kemnade 
Signed-off-by: Sebastian Reichel 
Signed-off-by: Sasha Levin