From: sashiko-bot@kernel.org
To: "Abel Vesa" <abel.vesa@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v4 1/3] arm64: dts: qcom: eliza: Describe the ADSP and USB related nodes
Date: Thu, 14 May 2026 03:30:21 +0000 [thread overview]
Message-ID: <20260514033021.D8B53C19425@smtp.kernel.org> (raw)
In-Reply-To: <20260513-eliza-adsp-usb-v4-1-839936e89aca@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Redundant `interrupt-parent` property alongside `interrupts-extended` in the `aoss_qmp` node.
--
commit 83bbc0567b448712af4a939b7fec5336a2e27452
Author: Abel Vesa <abel.vesa@oss.qualcomm.com>
arm64: dts: qcom: eliza: Describe the ADSP and USB related nodes
This commit adds the ADSP remoteproc node, USB controller, and their
dependencies such as the IPCC mailbox, QMP combo PHY, and SNPS eUSB2 PHY to
the Eliza SoC device tree.
> diff --git a/arch/arm64/boot/dts/qcom/eliza.dtsi b/arch/arm64/boot/dts/qcom/eliza.dtsi
> --- a/arch/arm64/boot/dts/qcom/eliza.dtsi
> +++ b/arch/arm64/boot/dts/qcom/eliza.dtsi
[ ... ]
> + aoss_qmp: power-management@c300000 {
> + compatible = "qcom,eliza-aoss-qmp", "qcom,aoss-qmp";
> + reg = <0x0 0x0c300000 0x0 0x400>;
> +
> + interrupt-parent = <&ipcc>;
> + interrupts-extended = <&ipcc IPCC_CLIENT_AOP IPCC_MPROC_SIGNAL_GLINK_QMP
> + IRQ_TYPE_EDGE_RISING>;
Is the interrupt-parent property necessary here?
Since interrupts-extended already explicitly provides the phandle to the
interrupt parent for the interrupt specifier, the interrupt-parent property
appears to be redundant and may trigger a dtc or schema validation warning.
> +
> + mboxes = <&ipcc IPCC_CLIENT_AOP IPCC_MPROC_SIGNAL_GLINK_QMP>;
> +
> + #clock-cells = <0>;
> + };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260513-eliza-adsp-usb-v4-0-839936e89aca@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-05-14 3:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 9:18 [PATCH v4 0/3] arm64: dts: qcom: eliza: Add ADSP and USB support Abel Vesa
2026-05-13 9:18 ` [PATCH v4 1/3] arm64: dts: qcom: eliza: Describe the ADSP and USB related nodes Abel Vesa
2026-05-13 9:43 ` Konrad Dybcio
2026-05-14 3:30 ` sashiko-bot [this message]
2026-05-13 9:18 ` [PATCH v4 2/3] arm64: dts: qcom: Add Eliza-specific PM7550BA dtsi Abel Vesa
2026-05-13 9:18 ` [PATCH v4 3/3] arm64: dts: qcom: eliza-mtp: Enable USB and ADSP support Abel Vesa
2026-05-14 4:04 ` 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=20260514033021.D8B53C19425@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=krzk+dt@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