[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <172477791953.367469.12003415047436890038.b4-ty@collabora.com>
Date: Tue, 27 Aug 2024 18:58:39 +0200
From: Sebastian Reichel <sebastian.reichel@...labora.com>
To: Hans de Goede <hdegoede@...hat.com>,
Krzysztof Kozlowski <krzk@...nel.org>,
Marek Szyprowski <m.szyprowski@...sung.com>,
Sebastian Krzyszkowiak <sebastian.krzyszkowiak@...i.sm>,
Purism Kernel Team <kernel@...i.sm>, Sebastian Reichel <sre@...nel.org>,
Anton Vorontsov <anton.vorontsov@...aro.org>,
Ramakrishna Pallala <ramakrishna.pallala@...el.com>,
Dirk Brandewie <dirk.brandewie@...il.com>,
Artur Weber <aweber.kernel@...il.com>
Cc: Henrik Grimler <henrik@...mler.se>, linux-pm@...r.kernel.org,
linux-kernel@...r.kernel.org, ~postmarketos/upstreaming@...ts.sr.ht
Subject: Re: [PATCH] power: supply: max17042_battery: Fix SOC threshold
calc w/ no current sense
On Sat, 17 Aug 2024 12:51:14 +0200, Artur Weber wrote:
> Commit 223a3b82834f ("power: supply: max17042_battery: use VFSOC for
> capacity when no rsns") made it so that capacity on systems without
> current sensing would be read from VFSOC instead of RepSOC. However,
> the SOC threshold calculation still read RepSOC to get the SOC
> regardless of the current sensing option state.
>
> Fix this by applying the same conditional to determine which register
> should be read.
>
> [...]
Applied, thanks!
[1/1] power: supply: max17042_battery: Fix SOC threshold calc w/ no current sense
commit: 3a3acf839b2cedf092bdd1ff65b0e9895df1656b
Best regards,
--
Sebastian Reichel <sebastian.reichel@...labora.com>
Powered by blists - more mailing lists