Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Richard Acayan" <mailingradian@gmail.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 04/11] dt-bindings: remoteproc: qcom: adsp: Add SDM670 ADSP compatible
Date: Sat, 03 Oct 2026 18:05:53 +0000	[thread overview]
Message-ID: <20261003180553.E5F651F0089B@smtp.kernel.org> (raw)
In-Reply-To: <20261003175659.23536-5-mailingradian@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dt-bindings: schema bypass due to compatible string in standalone enum
--

commit fe965abba1a50ee3f23c3149e9b465705dc13459
Author: Richard Acayan <mailingradian@gmail.com>

dt-bindings: remoteproc: qcom: adsp: Add SDM670 ADSP compatible

The commit adds the SDM670 ADSP compatible string to the qcom,adsp binding.
It splits the compatible property into a oneOf block to allow the SDM670
compatible to fallback to SDM845.

> diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,adsp.yaml b/Documentation/devicetree/bindings/remoteproc/qcom,adsp.yaml
> index 7e8ecae8e6cb6..6cf1f11efe041 100644
> --- a/Documentation/devicetree/bindings/remoteproc/qcom,adsp.yaml
> +++ b/Documentation/devicetree/bindings/remoteproc/qcom,adsp.yaml
> @@ -15,19 +15,26 @@ description:
>  
>  properties:
>    compatible:
[ ... ]
> +    oneOf:
> +      - enum:
> +          - qcom,msm8226-adsp-pil
[ ... ]
> +          - qcom,sdm660-cdsp-pas
> +          - qcom,sdm670-adsp-pas

[Severity: Medium]
Does adding qcom,sdm670-adsp-pas to this standalone enum branch bypass the
fallback requirement?

Because oneOf only requires a single branch to match, a device tree node
specifying only "qcom,sdm670-adsp-pas" matches this enum branch and passes
schema validation.

This bypasses the fallback enforcement in the items branch below, allowing
DTS nodes to be introduced without the required fallback string. Without
the fallback string, older kernels may fail to probe the device.

> +          - qcom,sdm845-adsp-pas
> +          - qcom,sdm845-cdsp-pas
> +          - qcom,sdm845-slpi-pas
> +
> +      - items:
> +          - enum:
> +              - qcom,sdm670-adsp-pas
> +          - const: qcom,sdm845-adsp-pas
>  
>    reg:
>      maxItems: 1

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261003175659.23536-1-mailingradian@gmail.com?part=4

  reply	other threads:[~2026-10-03 18:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-03 17:56 [PATCH v2 00/11] ADSP for SDM670 and sound on Google Pixel 3a Richard Acayan
2026-10-03 17:56 ` [PATCH v2 01/11] dt-bindings: soc: qcom,smp2p: add sleepstate support Richard Acayan
2026-10-03 17:56 ` [PATCH v2 02/11] dt-bindings: mailbox: qcom: Add SDM670 APCS compatible Richard Acayan
2026-10-03 17:56 ` [PATCH v2 03/11] dt-bindings: soc: qcom: aoss: Add compatible for SDM670 Richard Acayan
2026-10-03 17:56 ` [PATCH v2 04/11] dt-bindings: remoteproc: qcom: adsp: Add SDM670 ADSP compatible Richard Acayan
2026-10-03 18:05   ` sashiko-bot [this message]
2026-10-09  6:52   ` Krzysztof Kozlowski
2026-10-03 17:56 ` [PATCH v2 05/11] ASoC: dt-bindings: msm8916-digital-codec: Add SDM670 compatible Richard Acayan
2026-10-04  7:55   ` Krzysztof Kozlowski
2026-10-03 17:56 ` [PATCH v2 06/11] remoteproc: qcom: pas: Add SDM670 ADSP support Richard Acayan
2026-10-03 17:56 ` [PATCH v2 07/11] arm64: dts: qcom: sdm670: add adsp Richard Acayan
2026-10-03 18:08   ` sashiko-bot
2026-10-03 17:56 ` [PATCH v2 08/11] arm64: dts: qcom: sdm670-google: enable adsp Richard Acayan
2026-10-03 17:56 ` [PATCH v2 09/11] arm64: dts: qcom: pm660l: add analog audio codec Richard Acayan
2026-10-03 18:06   ` sashiko-bot
2026-10-03 17:56 ` [PATCH v2 10/11] arm64: dts: qcom: sdm670: add digital " Richard Acayan
2026-10-03 17:56 ` [PATCH v2 11/11] arm64: dts: qcom: sdm670-google: add sound card Richard Acayan
2026-10-03 18:11   ` sashiko-bot
2026-10-07 11:05 ` (subset) [PATCH v2 00/11] ADSP for SDM670 and sound on Google Pixel 3a Mark Brown

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=20261003180553.E5F651F0089B@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=mailingradian@gmail.com \
    --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