From: Fenglin Wu <fenglin.wu@oss.qualcomm.com>
To: Maud Spierings <maud_spierings@hotmail.com>,
devnull+fenglin.wu.oss.qualcomm.com@kernel.org
Cc: andersson@kernel.org, bryan.odonoghue@linaro.org,
conor+dt@kernel.org, david.collins@oss.qualcomm.com,
devicetree@vger.kernel.org, dmitry.baryshkov@oss.qualcomm.com,
gregkh@linuxfoundation.org, heikki.krogerus@linux.intel.com,
kernel@oss.qualcomm.com, konrad.dybcio@oss.qualcomm.com,
konradybcio@kernel.org, krzk+dt@kernel.org,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, linux-usb@vger.kernel.org,
me@kuruczgy.com, robh@kernel.org, sre@kernel.org,
subbaraman.narayanamurthy@oss.qualcomm.com
Subject: Re: [PATCH v3 8/8] arm64: dts: qcom: x1e80100-crd: Add charge limit nvmem
Date: Fri, 5 Sep 2025 09:03:50 +0800 [thread overview]
Message-ID: <af7cf6cc-d558-435e-b406-374ef92914a2@oss.qualcomm.com> (raw)
In-Reply-To: <AM7P189MB100958EDD985483DB1F32EC5E301A@AM7P189MB1009.EURP189.PROD.OUTLOOK.COM>
On 9/3/2025 4:41 PM, Maud Spierings wrote:
> Hi Fenglin,
>
>> Add nvmem cells for getting charge control thresholds if they have
>> been set previously.
>>
>> Signed-off-by: Fenglin Wu <fenglin.wu@oss.qualcomm.com>
>> ---
>> arch/arm64/boot/dts/qcom/x1-crd.dtsi | 2 ++
>> arch/arm64/boot/dts/qcom/x1e80100-pmics.dtsi | 20 ++++++++++++++++++++
>> 2 files changed, 22 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/x1-crd.dtsi
>> b/arch/arm64/boot/dts/qcom/x1-crd.dtsi
>> index
>> c9f0d505267081af66b0973fe6c1e33832a2c86b..8c3d30dd936ef9b12867971f5f237dd12484072d
>> 100644
>> --- a/arch/arm64/boot/dts/qcom/x1-crd.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/x1-crd.dtsi
>> @@ -82,6 +82,8 @@ 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..abf7afe5127d7b8b572513234e00009ce837837d
>> 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@75 {
>
> I think this is supposed to be @76 given the reg property below and
> the other ones above.
Thanks for catching it. I will address it in next patch.
>
>> + reg = <0x76 0x1>;
>> + };
>> + };
>> +
>> pmk8550_gpios: gpio@8800 {
>> compatible = "qcom,pmk8550-gpio", "qcom,spmi-gpio";
>> reg = <0xb800>;
>>
>> --
>> 2.34.1
>
> Kind regards,
> Maud
next prev parent reply other threads:[~2025-09-05 1:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-26 7:18 [PATCH v3 0/8] power: supply: Add several features support in qcom-battmgr driver Fenglin Wu via B4 Relay
2025-08-26 7:18 ` [PATCH v3 1/8] power: supply: core: Add resistance power supply property Fenglin Wu via B4 Relay
2025-08-26 7:18 ` [PATCH v3 2/8] power: supply: core: Add state_of_health " Fenglin Wu via B4 Relay
2025-08-26 7:18 ` [PATCH v3 3/8] power: supply: qcom_battmgr: Add resistance " Fenglin Wu via B4 Relay
2025-08-26 7:18 ` [PATCH v3 4/8] power: supply: qcom_battmgr: Add state_of_health property Fenglin Wu via B4 Relay
2025-08-26 7:18 ` [PATCH v3 5/8] power: supply: qcom_battmgr: update compats for SM8550 and X1E80100 Fenglin Wu via B4 Relay
2025-08-26 7:18 ` [PATCH v3 6/8] dt-bindings: soc: qcom,pmic-glink: Add charge limit nvmem properties Fenglin Wu via B4 Relay
2025-09-01 20:05 ` Rob Herring (Arm)
2025-08-26 7:18 ` [PATCH v3 7/8] power: supply: qcom_battmgr: Add charge control support Fenglin Wu via B4 Relay
2025-09-03 8:29 ` Neil Armstrong
2025-09-05 1:19 ` Fenglin Wu
2025-09-05 7:09 ` Neil Armstrong
2025-08-26 7:18 ` [PATCH v3 8/8] arm64: dts: qcom: x1e80100-crd: Add charge limit nvmem Fenglin Wu via B4 Relay
2025-09-03 8:41 ` Maud Spierings
2025-09-05 1:03 ` Fenglin Wu [this message]
2025-09-09 8:56 ` Konrad Dybcio
2025-09-03 8:57 ` [PATCH v3 0/8] power: supply: Add several features support in qcom-battmgr driver Neil Armstrong
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=af7cf6cc-d558-435e-b406-374ef92914a2@oss.qualcomm.com \
--to=fenglin.wu@oss.qualcomm.com \
--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=devnull+fenglin.wu.oss.qualcomm.com@kernel.org \
--cc=dmitry.baryshkov@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=maud_spierings@hotmail.com \
--cc=me@kuruczgy.com \
--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