From: sashiko-bot@kernel.org
To: "Neil Armstrong" <neil.armstrong@linaro.org>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v6 1/5] arm64: dts: qcom: pmk8550: add VADC node
Date: Tue, 21 Jul 2026 15:40:07 +0000 [thread overview]
Message-ID: <20260721154008.0C7321F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260721-topic-sm8x50-adc5-gen3-v6-1-a507f4a1e537@linaro.org>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The patch includes a non-existent header file `"qcom-adc5-gen3.h"` and uses undefined function-like macros for device tree node registers, which causes a fatal syntax error during device tree compilation.
--
--- Patch [1]: [PATCH v6 1/5] arm64: dts: qcom: pmk8550: add VADC node ---
commit 0e03aa4d4f8680856bf95a8ea645ca19c313f79d
Author: Neil Armstrong <neil.armstrong@linaro.org>
arm64: dts: qcom: pmk8550: add VADC node
This commit adds the VADC node and initial ADC channels for the pmk8550
device tree.
> diff --git a/arch/arm64/boot/dts/qcom/pmk8550.dtsi b/arch/arm64/boot/dts/qcom/pmk8550.dtsi
> --- a/arch/arm64/boot/dts/qcom/pmk8550.dtsi
> +++ b/arch/arm64/boot/dts/qcom/pmk8550.dtsi
> @@ -7,6 +7,7 @@
> #include <dt-bindings/input/linux-event-codes.h>
> #include <dt-bindings/interrupt-controller/irq.h>
> #include <dt-bindings/spmi/spmi.h>
> +#include "qcom-adc5-gen3.h"
[Severity: Low]
Is the qcom-adc5-gen3.h header missing from the tree? Including a file that
does not exist will cause a compilation error.
[ ... ]
> + pmk8550_vadc: adc@9000 {
> + compatible = "qcom,spmi-adc5-gen3";
> + reg = <0x9000>, <0x9100>;
> + interrupts-extended = <&spmi_bus 0x0 0x90 0x1 IRQ_TYPE_EDGE_RISING>,
> + <&spmi_bus 0x0 0x91 0x1 IRQ_TYPE_EDGE_RISING>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> + #io-channel-cells = <1>;
> + #thermal-sensor-cells = <1>;
> +
> + channel@0 {
> + reg = <ADC5_GEN3_REF_GND(0)>;
[Severity: Low]
Since the header is missing, will the preprocessor fail to expand the
ADC5_GEN3_REF_GND macro? This unexpanded text causes a syntax error when the
device tree compiler expects an integer value.
> + label = "pmk8550_offset_ref";
> + qcom,pre-scaling = <1 1>;
> + };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260721-topic-sm8x50-adc5-gen3-v6-0-a507f4a1e537@linaro.org?part=1
next prev parent reply other threads:[~2026-07-21 15:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 15:31 [PATCH v6 0/5] arm64: dts: qcom: sm8[56]50: add PMIC5 Gen3 ADC channels Neil Armstrong
2026-07-21 15:31 ` [PATCH v6 1/5] arm64: dts: qcom: pmk8550: add VADC node Neil Armstrong
2026-07-21 15:40 ` sashiko-bot [this message]
2026-07-21 15:31 ` [PATCH v6 2/5] arm64: dts: qcom: sm8550-qrd: add SPMI ADC channels and thermal nodes Neil Armstrong
2026-07-21 15:49 ` sashiko-bot
2026-07-21 15:31 ` [PATCH v6 3/5] arm64: dts: qcom: sm8550-hdk: " Neil Armstrong
2026-07-21 15:37 ` Konrad Dybcio
2026-07-21 16:04 ` sashiko-bot
2026-07-21 15:31 ` [PATCH v6 4/5] arm64: dts: qcom: sm8650-qrd: " Neil Armstrong
2026-07-21 15:54 ` sashiko-bot
2026-07-21 17:02 ` Konrad Dybcio
2026-07-21 15:31 ` [PATCH v6 5/5] arm64: dts: qcom: sm8650-hdk: " Neil Armstrong
2026-07-21 15:47 ` sashiko-bot
2026-07-21 17:02 ` Konrad Dybcio
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=20260721154008.0C7321F00A3A@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.