From: sashiko-bot@kernel.org
To: "Abel Vesa" <abel.vesa@oss.qualcomm.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: remoteproc: qcom,milos-pas: Move Eliza ADSP to SM8550 schema
Date: Wed, 22 Jul 2026 09:51:48 +0000 [thread overview]
Message-ID: <20260722095149.0C9DD1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260722-dts-qcom-eliza-fix-adsp-binding-v2-1-e1e98ae15533@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Moving `qcom,eliza-adsp-pas` to an items list requiring a fallback breaks backward compatibility and schema validation for the existing in-tree device tree.
--
--- Patch [1]: [PATCH v2 1/2] dt-bindings: remoteproc: qcom,milos-pas: Move Eliza ADSP to SM8550 schema ---
commit de0588624107f153559b1ce48e9d1f56b81467d0
Author: Abel Vesa <abel.vesa@oss.qualcomm.com>
dt-bindings: remoteproc: qcom,milos-pas: Move Eliza ADSP to SM8550 schema
The ADSP PAS found on Eliza SoC looks fully compatible with SM8750, which
can fallback to SM8550 except for the extra interrupt ("shutdown-ack").
So document its bindings in the SM8550 schema instead.
[ ... ]
> diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,sm8550-pas.yaml b/Documentation/devicetree/bindings/remoteproc/qcom,sm8550-pas.yaml
> index 2a4c527552e69..e6d81a38fd1c0 100644
> --- a/Documentation/devicetree/bindings/remoteproc/qcom,sm8550-pas.yaml
> +++ b/Documentation/devicetree/bindings/remoteproc/qcom,sm8550-pas.yaml
> @@ -29,6 +29,7 @@ properties:
> - qcom,x1e80100-cdsp-pas
> - items:
> - enum:
> + - qcom,eliza-adsp-pas
[Severity: Medium]
Will this break dtbs_check for existing device trees?
Looking at arch/arm64/boot/dts/qcom/eliza.dtsi, the compatible string is
currently defined without the newly required fallback:
arch/arm64/boot/dts/qcom/eliza.dtsi:
remoteproc_adsp: remoteproc@3000000 {
compatible = "qcom,eliza-adsp-pas";
Since this schema change now strictly requires the items array to include
the qcom,sm8550-adsp-pas fallback string, does this break backward
compatibility and cause schema validation to fail for the existing in-tree
device tree?
> - qcom,glymur-adsp-pas
> - qcom,hawi-adsp-pas
> - qcom,kaanapali-adsp-pas
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260722-dts-qcom-eliza-fix-adsp-binding-v2-0-e1e98ae15533@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-07-22 9:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 9:40 [PATCH v2 0/2] dt-bindings: remoteproc: qcom,milos-pas: Fix ADSP bindings Abel Vesa
2026-07-22 9:40 ` [PATCH v2 1/2] dt-bindings: remoteproc: qcom,milos-pas: Move Eliza ADSP to SM8550 schema Abel Vesa
2026-07-22 9:51 ` sashiko-bot [this message]
2026-07-22 10:05 ` Abel Vesa
2026-07-22 9:40 ` [PATCH v2 2/2] arm64: dts: qcom: eliza: Add fallback compatible for ADSP remoteproc 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=20260722095149.0C9DD1F000E9@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 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.