From: sashiko-bot@kernel.org
To: "Neil Armstrong" <neil.armstrong@linaro.org>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 4/5] arm64: dts: qcom: sm8650-qrd: add SPMI ADC channels and thermal nodes
Date: Thu, 02 Jul 2026 10:57:17 +0000 [thread overview]
Message-ID: <20260702105718.13ABF1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260702-topic-sm8x50-adc5-gen3-v5-4-8169953634ad@linaro.org>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] The devicetree node `channel@503` for the PM8550VE ADC channel has a unit address that does not match its `reg` property.
- [Low] The patch relies on a missing devicetree header `qcom-adc5-gen3.h` and undeclared function-like macros, causing a fatal dtc build error.
--
commit a2bc49ac04a87d9b25a3326a56b79fa449a81ea9
Author: Neil Armstrong <neil.armstrong@linaro.org>
arm64: dts: qcom: sm8650-qrd: add SPMI ADC channels and thermal nodes
Add the SPMI ADC channels on the PMK8550 SPMI5 ADC3 for the
other PMICS on the system. The thermal nodes are sorted by the sensor
channel to be coherent with the system thermal nodes ordering.
> diff --git a/arch/arm64/boot/dts/qcom/sm8650-qrd.dts b/arch/arm64/boot/dts/qcom/sm8650-qrd.dts
> index a3982ae229290..ba63bfc78e6ef 100644
> --- a/arch/arm64/boot/dts/qcom/sm8650-qrd.dts
> +++ b/arch/arm64/boot/dts/qcom/sm8650-qrd.dts
[ ... ]
> @@ -1040,27 +1126,218 @@ led@3 {
> };
> };
>
> +&pm8550_temp_alarm {
> + io-channels = <&pmk8550_vadc ADC5_GEN3_DIE_TEMP(1)>;
[Severity: Low]
Does this rely on a missing header for ADC5_GEN3_DIE_TEMP()?
It looks like the included header qcom-adc5-gen3.h is missing from this patch
series and the kernel tree.
Additionally, ADC5_GEN3_DIE_TEMP is defined as a constant without arguments in
qcom-adc5-gen3-common.h, so passing it an argument like (1) results in a C
preprocessor syntax error and causes a fatal dtc compilation failure.
> + io-channel-names = "thermal";
> +};
> +
[ ... ]
> + /* PM8550VS_E Channel nodes */
> + channel@403 {
> + reg = <ADC5_GEN3_DIE_TEMP(4)>;
> + label = "pm8550vs_e_die_temp";
> + qcom,pre-scaling = <1 1>;
> + };
> +
> + /* PM8550VE Channel nodes */
> + channel@503 {
> + reg = <ADC5_GEN3_DIE_TEMP(PMK8550VE_SID)>;
[Severity: Low]
Is there a mismatch between the unit address and the reg property here?
The PMK8550VE_SID macro evaluates to 8, which means the reg property
evaluates to 0x803. The node is named channel@503, but the specification
requires the unit address to strictly match the first address in the reg
property.
Should this be named channel@803 to prevent a unit_address_vs_reg compiler
warning?
> + label = "pm8550ve_die_temp";
> + qcom,pre-scaling = <1 1>;
> + };
> +
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260702-topic-sm8x50-adc5-gen3-v5-0-8169953634ad@linaro.org?part=4
next prev parent reply other threads:[~2026-07-02 10:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 9:48 [PATCH v5 0/5] arm64: dts: qcom: sm8[56]50: add PMIC5 Gen3 ADC channels Neil Armstrong
2026-07-02 9:48 ` [PATCH v5 1/5] arm64: dts: qcom: pmk8550: add VADC node Neil Armstrong
2026-07-02 10:02 ` sashiko-bot
2026-07-02 9:48 ` [PATCH v5 2/5] arm64: dts: qcom: sm8550-qrd: add SPMI ADC channels and thermal nodes Neil Armstrong
2026-07-02 10:16 ` sashiko-bot
2026-07-02 9:48 ` [PATCH v5 3/5] arm64: dts: qcom: sm8550-hdk: " Neil Armstrong
2026-07-02 10:35 ` sashiko-bot
2026-07-02 9:48 ` [PATCH v5 4/5] arm64: dts: qcom: sm8650-qrd: " Neil Armstrong
2026-07-02 10:57 ` sashiko-bot [this message]
2026-07-02 9:48 ` [PATCH v5 5/5] arm64: dts: qcom: sm8650-hdk: " Neil Armstrong
2026-07-02 11:20 ` sashiko-bot
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=20260702105718.13ABF1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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