All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "David Heidelberg" <david@ixit.cz>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: arm: qcom: Add Xiaomi Mi 8 family compatibles
Date: Sun, 09 Aug 2026 16:56:05 +0000	[thread overview]
Message-ID: <20260809165606.000971F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260809-dipper-v1-1-eb4d501e85df@ixit.cz>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The compatible string `xiaomi,dipper` is added to two mutually exclusive schema blocks with conflicting constraints, allowing incomplete compatible lists to silently pass validation.
--

--- Patch [1]: [PATCH 1/2] dt-bindings: arm: qcom: Add Xiaomi Mi 8 family compatibles ---
commit 303d802416f225c92da471f33c7f3f2a3dcb2b9c
Author: David Heidelberg <david@ixit.cz>
dt-bindings: arm: qcom: Add Xiaomi Mi 8 family compatibles

This commit adds device tree binding compatibles for the Xiaomi Mi 8 smartphone
family, codenamed dipper, and documents variants such as ursa and equuleus.

> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> index ff8a35df7862d..6309f8ab02fba 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> @@ -950,6 +950,15 @@ properties:
>            - const: google,bonito
>            - const: qcom,sdm670
>  
> +      - description: Xiaomi Mi 8 family
> +        items:
> +          - enum:
> +              - xiaomi,dipper
> +              - xiaomi,equuleus
> +              - xiaomi,ursa
> +          - const: xiaomi,dipper-common
> +          - const: qcom,sdm845
> +

[ ... ]

> @@ -976,6 +985,7 @@ properties:
>                - sony,akatsuki-row
>                - sony,apollo-row
>                - thundercomm,db845c
> +              - xiaomi,dipper
>                - xiaomi,polaris
>            - const: qcom,sdm845

[Severity: Medium]
Was xiaomi,dipper mistakenly added to this 2-element block as well?

Since xiaomi,dipper is already defined in the 3-element Xiaomi Mi 8 family
block above, adding it here introduces a regression in schema validation.
A device tree using an incomplete compatible array like 
["xiaomi,dipper", "qcom,sdm845"] will pass schema validation by matching this
block, completely bypassing the requirement for the "xiaomi,dipper-common"
fallback string.

Would removing it from this generic list ensure the intermediate fallback is
properly enforced for the dipper board?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260809-dipper-v1-0-eb4d501e85df@ixit.cz?part=1

  reply	other threads:[~2026-08-09 16:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-09 16:48 [PATCH 0/2] Introduce support for Xiaomi Mi 8 David Heidelberg via B4 Relay
2026-08-09 16:48 ` David Heidelberg
2026-08-09 16:48 ` [PATCH 1/2] dt-bindings: arm: qcom: Add Xiaomi Mi 8 family compatibles David Heidelberg via B4 Relay
2026-08-09 16:48   ` David Heidelberg
2026-08-09 16:56   ` sashiko-bot [this message]
2026-08-09 17:05     ` David Heidelberg
2026-08-09 16:48 ` [PATCH 2/2] arm64: dts: qcom: add Xiaomi Mi 8 (dipper) David Heidelberg via B4 Relay
2026-08-09 16:48   ` David Heidelberg

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=20260809165606.000971F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=david@ixit.cz \
    --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.