diff options
| author | Konrad Dybcio <konrad.dybcio@linaro.org> | 2023-12-18 15:41:52 +0100 |
|---|---|---|
| committer | Sebastian Reichel <sebastian.reichel@collabora.com> | 2023-12-25 00:02:03 +0100 |
| commit | b43f7ddc2b7a5a90447d96cb4d3c6d142dd4a810 (patch) | |
| tree | 89e3b194cf29a8a606b6b34643eeb546899857ba /scripts/gdb/linux/lists.py | |
| parent | 523100208bd22e3eee7b76025ee4584b5d1ea0ee (diff) | |
power: supply: qcom_battmgr: Register the power supplies after PDR is up
Currently, a not-yet-entirely-initialized battmgr (e.g. with pd-mapper
not having yet started or ADSP not being up etc.) results in a couple of
zombie power supply devices hanging around.
This is particularly noticeable when trying to suspend the device (even
s2idle): the PSY-internal thermal zone is inaccessible and returns
-ENODEV, which causes log spam.
Register the power supplies only after we received some notification
indicating battmgr is ready to take off.
Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
Tested-by: Luca Weiss <luca.weiss@fairphone.com>
Link: https://lore.kernel.org/r/20231218-topic-battmgr_fixture_attempt-v1-1-6145745f34fe@linaro.org
Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>
Diffstat (limited to 'scripts/gdb/linux/lists.py')
0 files changed, 0 insertions, 0 deletions