[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <509d5d7d-b7a3-4dc9-b3e6-c3e52abe040c@oss.qualcomm.com>
Date: Fri, 5 Dec 2025 12:51:46 +0100
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: Erikas Bitovtas <xerikasxx@...il.com>,
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>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, ~postmarketos/upstreaming@...ts.sr.ht,
phone-devel@...r.kernel.org
Subject: Re: [PATCH v2 1/2] arm64: dts: qcom: msm8939-asus-z00t: add battery
On 11/21/25 12:10 AM, Erikas Bitovtas wrote:
> This device tracks remaining battery capacity percentage using voltage
> mode BMS. This commit enables the pm8916_bms node and adds a battery
> node to track its capacity. Battery properties were taken from the
> information printed on the battery itself and downstream device tree
> for a battery named "nvt+atl_3000mah" [1]
>
> [1] https://github.com/Asus-MSM8916/android_kernel_asus_msm8916/blob/10.x/arch/arm/boot/dts/qcom/ASUS_ZE550KL_1936167_3000mAh_3p4COV_VBMS_Final.dtsi
>
> Signed-off-by: Erikas Bitovtas <xerikasxx@...il.com>
> ---
> arch/arm64/boot/dts/qcom/msm8939-asus-z00t.dts | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/qcom/msm8939-asus-z00t.dts b/arch/arm64/boot/dts/qcom/msm8939-asus-z00t.dts
> index ebb548e62e02..b58f0a04abfd 100644
> --- a/arch/arm64/boot/dts/qcom/msm8939-asus-z00t.dts
> +++ b/arch/arm64/boot/dts/qcom/msm8939-asus-z00t.dts
> @@ -20,6 +20,25 @@ aliases {
> serial0 = &blsp_uart2;
> };
>
> + battery: battery {
> + compatible = "simple-battery";
> + device-chemistry = "lithium-ion-polymer";
> + voltage-min-design-microvolt = <3400000>;
> + voltage-max-design-microvolt = <4400000>;
> + energy-full-design-microwatt-hours = <11500000>;
> + charge-full-design-microamp-hours = <3000000>;
> +
> + ocv-capacity-celsius = <25>;
> + ocv-capacity-table-0 = <4372000 100>, <4306000 95>, <4247000 90>,
> + <4190000 85>, <4134000 80>, <4081000 75>, <4030000 70>,
> + <3984000 65>, <3930000 60>, <3884000 55>, <3850000 50>,
> + <3826000 45>, <3804000 40>, <3786000 35>, <3770000 30>,
> + <3753000 25>, <3734000 20>, <3712000 16>, <3693000 13>,
> + <3686000 11>, <3684000 10>, <3682000 9>, <3680000 8>,
> + <3676000 7>, <3668000 6>, <3643000 5>, <3600000 4>,
> + <3542000 3>, <3462000 2>, <3340000 1>, <3000000 0>;
I was surprised to learn the binding allows you to specify the OCV table
for multiple temperature points (your downstream provides -20/0/25/40/60)
May I ask you to fill in that data?
Konrad
Powered by blists - more mailing lists