From: Fenglin Wu via B4 Relay <devnull+fenglin.wu.oss.qualcomm.com@kernel.org>
To: Sebastian Reichel <sre@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Cc: "Subbaraman Narayanamurthy"
<subbaraman.narayanamurthy@oss.qualcomm.com>,
"David Collins" <david.collins@oss.qualcomm.com>,
"György Kurucz" <me@kuruczgy.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org, kernel@oss.qualcomm.com,
devicetree@vger.kernel.org, linux-usb@vger.kernel.org,
"Fenglin Wu" <fenglin.wu@oss.qualcomm.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>
Subject: [PATCH v5 8/9] arm64: dts: qcom: x1e80100-crd: Add charge limit nvmem
Date: Wed, 17 Sep 2025 18:15:21 +0800 [thread overview]
Message-ID: <20250917-qcom_battmgr_update-v5-8-270ade9ffe13@oss.qualcomm.com> (raw)
In-Reply-To: <20250917-qcom_battmgr_update-v5-0-270ade9ffe13@oss.qualcomm.com>
From: Fenglin Wu <fenglin.wu@oss.qualcomm.com>
Add nvmem cells for getting charge control thresholds if they have
been set previously.
Tested-by: Neil Armstrong <neil.armstrong@linaro.org> # on Thinkpad T14S OLED
Reviewed-by: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Signed-off-by: Fenglin Wu <fenglin.wu@oss.qualcomm.com>
---
arch/arm64/boot/dts/qcom/x1-crd.dtsi | 7 +++++++
arch/arm64/boot/dts/qcom/x1e80100-pmics.dtsi | 20 ++++++++++++++++++++
2 files changed, 27 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/x1-crd.dtsi b/arch/arm64/boot/dts/qcom/x1-crd.dtsi
index c9f0d505267081af66b0973fe6c1e33832a2c86b..cd3c071624ce66f8c28ee4521fe3db8b737757a6 100644
--- a/arch/arm64/boot/dts/qcom/x1-crd.dtsi
+++ b/arch/arm64/boot/dts/qcom/x1-crd.dtsi
@@ -82,6 +82,13 @@ pmic-glink {
<&tlmm 123 GPIO_ACTIVE_HIGH>,
<&tlmm 125 GPIO_ACTIVE_HIGH>;
+ nvmem-cells = <&charge_limit_en>,
+ <&charge_limit_end>,
+ <&charge_limit_delta>;
+ nvmem-cell-names = "charge_limit_en",
+ "charge_limit_end",
+ "charge_limit_delta";
+
/* Left-side rear port */
connector@0 {
compatible = "usb-c-connector";
diff --git a/arch/arm64/boot/dts/qcom/x1e80100-pmics.dtsi b/arch/arm64/boot/dts/qcom/x1e80100-pmics.dtsi
index c02fd4d15c9649c222caaafa5ed2c777a10fb4f5..eb5562e4393c88faa16d9172ee2a1ceabef076ff 100644
--- a/arch/arm64/boot/dts/qcom/x1e80100-pmics.dtsi
+++ b/arch/arm64/boot/dts/qcom/x1e80100-pmics.dtsi
@@ -239,6 +239,26 @@ reboot_reason: reboot-reason@48 {
};
};
+ pmk8550_sdam_15: nvram@7e00 {
+ compatible = "qcom,spmi-sdam";
+ reg = <0x7e00>;
+ #address-cells = <1>;
+ #size-cells = <1>;
+ ranges = <0 0x7e00 0x100>;
+
+ charge_limit_en: charge-limit-en@73 {
+ reg = <0x73 0x1>;
+ };
+
+ charge_limit_end: charge-limit-end@75 {
+ reg = <0x75 0x1>;
+ };
+
+ charge_limit_delta: charge-limit-delta@76 {
+ reg = <0x76 0x1>;
+ };
+ };
+
pmk8550_gpios: gpio@8800 {
compatible = "qcom,pmk8550-gpio", "qcom,spmi-gpio";
reg = <0xb800>;
--
2.34.1
next prev parent reply other threads:[~2025-09-17 10:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 10:15 [PATCH v5 0/9] power: supply: Add several features support in qcom-battmgr driver Fenglin Wu via B4 Relay
2025-09-17 10:15 ` [PATCH v5 1/9] power: supply: core: Add resistance power supply property Fenglin Wu via B4 Relay
2025-09-17 10:15 ` [PATCH v5 2/9] power: supply: core: Add state_of_health " Fenglin Wu via B4 Relay
2025-09-17 10:15 ` [PATCH v5 3/9] power: supply: qcom_battmgr: Add resistance " Fenglin Wu via B4 Relay
2025-09-17 10:15 ` [PATCH v5 4/9] power: supply: qcom_battmgr: Add state_of_health property Fenglin Wu via B4 Relay
2025-09-17 10:15 ` [PATCH v5 5/9] power: supply: qcom_battmgr: update compats for SM8550 and X1E80100 Fenglin Wu via B4 Relay
2025-09-17 10:15 ` [PATCH v5 6/9] dt-bindings: soc: qcom,pmic-glink: Add charge limit nvmem properties Fenglin Wu via B4 Relay
2025-09-17 10:15 ` [PATCH v5 7/9] power: supply: qcom_battmgr: Add charge control support Fenglin Wu via B4 Relay
2025-09-17 10:15 ` Fenglin Wu via B4 Relay [this message]
2025-09-17 10:15 ` [PATCH v5 9/9] power: supply: qcom_battmgr: handle charging state change notifications Fenglin Wu via B4 Relay
2025-09-17 11:14 ` Konrad Dybcio
2025-09-18 2:01 ` Fenglin Wu
2025-09-18 23:17 ` Sebastian Reichel
2025-09-17 23:03 ` (subset) [PATCH v5 0/9] power: supply: Add several features support in qcom-battmgr driver Sebastian Reichel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250917-qcom_battmgr_update-v5-8-270ade9ffe13@oss.qualcomm.com \
--to=devnull+fenglin.wu.oss.qualcomm.com@kernel.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=david.collins@oss.qualcomm.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=fenglin.wu@oss.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=kernel@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=me@kuruczgy.com \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=sre@kernel.org \
--cc=subbaraman.narayanamurthy@oss.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox