From: Jishnu Prakash <jishnu.prakash@oss.qualcomm.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
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>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Ayyagari Ushasreevalli <aushasre@qti.qualcomm.com>,
Kamal Wadhwa <kamal.wadhwa@oss.qualcomm.com>
Subject: Re: [PATCH 2/3] arm64: dts: qcom: lemans-pmics: Add ADC support for PMM8654au
Date: Thu, 18 Jun 2026 15:51:44 +0530 [thread overview]
Message-ID: <5941078e-2376-46a4-b9e2-9686de1ca991@oss.qualcomm.com> (raw)
In-Reply-To: <57f3407f-3371-4db7-87cc-218f7360ce3f@oss.qualcomm.com>
Hi Konrad,
On 6/15/2026 9:26 PM, Konrad Dybcio wrote:
> On 4/30/26 10:58 AM, Jishnu Prakash wrote:
>> From: Ayyagari Ushasreevalli <aushasre@qti.qualcomm.com>
>>
>> Add ADC nodes for the four PMM8654au PMICs (pmm8654au_0 through
>> pmm8654au_3) on the Lemans platform.
>>
>> Each ADC node exposes the following ADC channels:
>> - DIE_TEMP: PMIC die temperature channel
>> - VPH_PWR: Battery/supply voltage channel
>>
>> Also add the io-channels and io-channel-names properties under
>> the temp-alarm nodes so that they can get temperature reading
>> from the ADC die_temp channels.
>>
>> Signed-off-by: Ayyagari Ushasreevalli <aushasre@qti.qualcomm.com>
>> Signed-off-by: Jishnu Prakash <jishnu.prakash@oss.qualcomm.com>
>> ---
>> arch/arm64/boot/dts/qcom/lemans-pmics.dtsi | 93 ++++++++++++++++++++++++++++++
>> 1 file changed, 93 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/qcom/lemans-pmics.dtsi b/arch/arm64/boot/dts/qcom/lemans-pmics.dtsi
>> index 341119fc8244..6caec3e4df4b 100644
>> --- a/arch/arm64/boot/dts/qcom/lemans-pmics.dtsi
>> +++ b/arch/arm64/boot/dts/qcom/lemans-pmics.dtsi
>> @@ -5,6 +5,7 @@
>>
>> #include <dt-bindings/input/input.h>
>> #include <dt-bindings/spmi/spmi.h>
>> +#include "qcom-adc5-gen3.h"
>>
>> / {
>> thermal-zones {
>> @@ -110,6 +111,8 @@ pmm8654au_0_temp_alarm: temp-alarm@a00 {
>> reg = <0xa00>;
>> interrupts-extended = <&spmi_bus 0x0 0xa 0x0 IRQ_TYPE_EDGE_BOTH>;
>> #thermal-sensor-cells = <0>;
>> + io-channels = <&pmm8654au_0_adc ADC5_GEN3_DIE_TEMP(0)>;
>> + io-channel-names = "thermal";
>> };
>>
>> pmm8654au_0_pon: pon@1200 {
>> @@ -141,6 +144,27 @@ pmm8654au_0_rtc: rtc@6100 {
>> interrupts = <0x0 0x62 0x1 IRQ_TYPE_EDGE_RISING>;
>> };
>>
>> + pmm8654au_0_adc: adc@8000 {
>> + compatible = "qcom,spmi-adc5-gen3";
>> + reg = <0x8000>;
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + interrupts = <0x0 0x80 0x1 IRQ_TYPE_EDGE_RISING>;
>> + #io-channel-cells = <1>;
>> +
>> + channel@3 {
>> + reg = <ADC5_GEN3_DIE_TEMP(0)>;
>> + label = "pmm8654au_0_die_temp";
>
> Are these labels namespaced, i.e. can the label be just "pm8654au_die_temp"
> or "die_temp"?
From what I see, there's no functional issue with updating the label to either
of the names you suggested. We made it this way at first as we thought it would
be useful to have the exact PMIC instance name in the label of each channel.
Do you want any changes in the labels? If yes, which convention do you prefer?
Thanks,
Jishnu
>
> Konrad
next prev parent reply other threads:[~2026-06-18 10:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 8:58 [PATCH 0/3] Add ADC support for lemans and monaco Jishnu Prakash
2026-04-30 8:58 ` [PATCH 1/3] arm64: dts: qcom: Add header file for ADC5 Gen3 channel macros Jishnu Prakash
2026-06-15 15:55 ` Konrad Dybcio
2026-06-15 16:39 ` Neil Armstrong
2026-06-15 16:48 ` Konrad Dybcio
2026-06-17 10:12 ` Neil Armstrong
2026-04-30 8:58 ` [PATCH 2/3] arm64: dts: qcom: lemans-pmics: Add ADC support for PMM8654au Jishnu Prakash
2026-06-15 15:56 ` Konrad Dybcio
2026-06-18 10:21 ` Jishnu Prakash [this message]
2026-06-30 11:57 ` Konrad Dybcio
2026-04-30 8:58 ` [PATCH 3/3] arm64: dts: qcom: monaco-pmics: Add ADC support for PMM8620AU Jishnu Prakash
2026-04-30 9:12 ` [PATCH 0/3] Add ADC support for lemans and monaco 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=5941078e-2376-46a4-b9e2-9686de1ca991@oss.qualcomm.com \
--to=jishnu.prakash@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=aushasre@qti.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kamal.wadhwa@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=robh@kernel.org \
/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
all inboxes | Powered by JetHome®