Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Shawn Guo" <shengchao.guo@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v3 RESEND 4/5] dt-bindings: arm: qcom: Document SA8797P Ride board
Date: Tue, 26 May 2026 06:11:31 +0000	[thread overview]
Message-ID: <20260526061131.824601F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260526051300.1669201-5-shengchao.guo@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The compatible block for the SA8797P Ride board is inserted out of alphabetical order, breaking the established grouping of SoC families.
--

commit 4ab172bb1d1115af0854e9ac9febc931197a537f
Author: Shawn Guo <shengchao.guo@oss.qualcomm.com>

dt-bindings: arm: qcom: Document SA8797P Ride board

This commit documents the SA8797P Ride automotive-grade development
board, which is built on the SA8797P SoC (Nord series). It adds the
compatible string for the board with fallbacks to the SoC and series
compatibles.

> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> index 50cc18a6ec5ed..b10383ddb8991 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> @@ -303,6 +303,12 @@ properties:
>                - xiaomi,sagit
>            - const: qcom,msm8998
>  
> +      - items:
> +          - enum:
> +              - qcom,sa8797p-ride
> +          - const: qcom,sa8797p
> +          - const: qcom,nord
> +

[Severity: Low]
Does this compatible block belong further down in the file? This isn't a
bug, but the compatibles under properties are generally grouped and
sorted alphanumerically. Placing this sa prefix block after msm8998 and
before the following entries breaks the alphabetical order of the SoC
families.

>        - items:
>            - enum:
>                - 8dev,jalapeno

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260526051300.1669201-1-shengchao.guo@oss.qualcomm.com?part=4

  reply	other threads:[~2026-05-26  6:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26  5:12 [PATCH v3 RESEND 0/5] Add initial device trees for Nord SA8797P Shawn Guo
2026-05-26  5:12 ` [PATCH v3 RESEND 1/5] dt-bindings: crypto: qcom,inline-crypto-engine: Document Nord ICE Shawn Guo
2026-05-26  5:12 ` [PATCH v3 RESEND 2/5] arm64: dts: qcom: Add device tree for Nord SoC series Shawn Guo
2026-05-26  5:44   ` sashiko-bot
2026-05-26  5:12 ` [PATCH v3 RESEND 3/5] arm64: dts: qcom: Add device tree for Nord SA8797P SoC Shawn Guo
2026-05-26  6:01   ` sashiko-bot
2026-05-26  5:12 ` [PATCH v3 RESEND 4/5] dt-bindings: arm: qcom: Document SA8797P Ride board Shawn Guo
2026-05-26  6:11   ` sashiko-bot [this message]
2026-05-26  5:13 ` [PATCH v3 RESEND 5/5] arm64: dts: qcom: Add device tree for " Shawn Guo
2026-05-26  6:29   ` 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=20260526061131.824601F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=shengchao.guo@oss.qualcomm.com \
    /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