[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8bb3a056-c00f-4ae0-a790-d742d31f229a@oss.qualcomm.com>
Date: Tue, 3 Jun 2025 13:48:11 +0800
From: Fenglin Wu <fenglin.wu@....qualcomm.com>
To: György Kurucz <me@...uczgy.com>,
Sebastian Reichel <sre@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley
<conor+dt@...nel.org>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Subbaraman Narayanamurthy <subbaraman.narayanamurthy@....qualcomm.com>,
David Collins <david.collins@....qualcomm.com>,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-msm@...r.kernel.org, kernel@....qualcomm.com,
devicetree@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: [PATCH v2 5/8] power: supply: qcom_battmgr: Add charge control
support
On 5/31/2025 6:36 PM, György Kurucz wrote:
>> Add charge control support for SM8550 and X1E80100.
>
> Thank you for this, tested on my Lenovo Yoga Slim 7x, the limiting
> works well, I finally don't have to worry about leaving my laptop
> plugged in for too long.
>
> One small thing I noticed is that after setting the sysfs values and
> rebooting, they report 0 again. The limiting appears to stay in effect
> though, so it seems that the firmware does keep the values, but Linux
> does not read them back. Indeed, looking at the code, it seems that
> actually reading back the values is only implemented for the SM8550.
Right.
Based on offline information, X1E80100 doesn't support reading back
those threshold values in battery management firmware, so I can only use
the cached values for sysfs read.
>
> Anyway, this is just a small nitpick, this does not really affect the
> functionality, and I would support merging this series regardless of
> whether the read back values are always correct.
>
> György
Powered by blists - more mailing lists