From: sashiko-bot@kernel.org
To: "Abel Vesa" <abel.vesa@oss.qualcomm.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 2/3] arm64: dts: qcom: Add Eliza CQS SoM platform
Date: Tue, 09 Jun 2026 08:12:08 +0000 [thread overview]
Message-ID: <20260609081210.097C91F00898@smtp.kernel.org> (raw)
In-Reply-To: <20260609-eliza-dts-qcs-evk-v3-2-b4e9b033a6dc@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] The device tree source includes `pm7550ba-eliza.dtsi`, which does not exist in the source tree, causing a C preprocessor failure during compilation.
- [Low] References to device tree labels `&sdhc_1`, `&sdc1_default`, `&sdc1_sleep`, and `&remoteproc_adsp` lack definitions in the base SoC device tree (`eliza.dtsi`).
--
commit 49ba8d899e255d89a8013a6ccd6b518c9f069ea6
Author: Abel Vesa <abel.vesa@oss.qualcomm.com>
arm64: dts: qcom: Add Eliza CQS SoM platform
This commit adds the Eliza CQS System-on-Module DTSI file. It describes
the regulators, board clocks, eMMC support, and ADSP firmware.
> diff --git a/arch/arm64/boot/dts/qcom/eliza-cqs-som.dtsi b/arch/arm64/boot/dts/qcom/eliza-cqs-som.dtsi
> new file mode 100644
> index 0000000000000..33f4cd2822724
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/eliza-cqs-som.dtsi
> @@ -0,0 +1,394 @@
> +// SPDX-License-Identifier: BSD-3-Clause
> +/*
> + * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries.
> + */
> +
> +#include <dt-bindings/gpio/gpio.h>
> +#include <dt-bindings/pinctrl/qcom,pmic-gpio.h>
> +#include <dt-bindings/regulator/qcom,rpmh-regulator.h>
> +
> +#include "eliza.dtsi"
> +#include "pm7550ba-eliza.dtsi"
[Severity: Low]
Is pm7550ba-eliza.dtsi missing from the tree? It doesn't appear to be added
in this commit or present in the baseline, which causes a preprocessor
failure during compilation.
[ ... ]
> +&remoteproc_adsp {
> + firmware-name = "qcom/eliza/adsp.mbn",
> + "qcom/eliza/adsp_dtb.mbn";
> +
> + status = "okay";
> +};
[Severity: Low]
Is the &remoteproc_adsp label defined in the base eliza.dtsi? Compiling
this device tree fails with a reference to a non-existent node or label.
> +
> +&sdhc_1 {
> + vmmc-supply = <&vreg_l12b>;
> + vqmmc-supply = <&vreg_l1d>;
> + pinctrl-0 = <&sdc1_default>;
> + pinctrl-1 = <&sdc1_sleep>;
> + pinctrl-names = "default", "sleep";
[Severity: Low]
Are the labels &sdhc_1, &sdc1_default, and &sdc1_sleep defined? They appear
to be missing from eliza.dtsi and the included files, leading to a build
failure.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260609-eliza-dts-qcs-evk-v3-0-b4e9b033a6dc@oss.qualcomm.com?part=2
next prev parent reply other threads:[~2026-06-09 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 8:00 [PATCH v3 0/3] arm64: dts: qcom: Add Eliza CQS EVK support Abel Vesa
2026-06-09 8:00 ` [PATCH v3 1/3] dt-bindings: arm: qcom: Document Eliza CQS SoM and its EVK board Abel Vesa
2026-06-09 8:00 ` [PATCH v3 2/3] arm64: dts: qcom: Add Eliza CQS SoM platform Abel Vesa
2026-06-09 8:12 ` sashiko-bot [this message]
2026-06-09 8:55 ` Abel Vesa
2026-06-09 8:00 ` [PATCH v3 3/3] arm64: dts: qcom: Add Eliza CQS EVK board Abel Vesa
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=20260609081210.097C91F00898@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=abel.vesa@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.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