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 v13 4/6] dt-bindings: arm: qcom: Document Nord reference boards
Date: Fri, 28 Aug 2026 04:03:03 +0000 [thread overview]
Message-ID: <20260828040304.0E3161F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260828034958.3165-5-shengchao.guo@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The root compatible binding omits the specific SoC compatible strings (qcom,sa8797p and qcom,iq10), forcing a 2-item array that breaks SoC-specific matching.
--
commit e7840dc716d1200acb611d432fcd24729d2913ba
Author: Shawn Guo <shengchao.guo@oss.qualcomm.com>
dt-bindings: arm: qcom: Document Nord reference boards
Nord is a new generation of SoC series from Qualcomm which includes SA8797P and
Dragonwing IQ10. This commit documents the SA8797P Ride and IQ10 Robotics
Reference Design (RRD) boards.
> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> index ff8a35df7862d..198314ddaa84a 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> @@ -402,6 +402,12 @@ properties:
> - xiaomi,sagit
> - const: qcom,msm8998
>
> + - items:
> + - enum:
> + - qcom,iq10-rrd
> + - qcom,sa8797p-ride
> + - const: qcom,nord
[Severity: Medium]
Does this strict 2-item array intentionally omit the specific SoC compatible
strings (qcom,sa8797p and qcom,iq10)?
Standard Device Tree practice usually requires the exact SoC string to be
present in the root compatible array before the generic family fallback. By
enforcing a 2-item array, the schema requires the device tree to omit the
specific SoC strings.
This prevents SoC-level drivers (like cpufreq-dt-platdev or qcom_pd_mapper)
from matching the specific SoC or applying quirks without hardcoding every
single board compatible. Note that qcom,sa8797p is actively used as an SoC
identifier for IP blocks (e.g., qcom,sa8797p-geni-spi).
Could the binding be updated to include the specific SoC strings as an
intermediate fallback before qcom,nord?
> +
> - description: Qualcomm Technologies, Inc. Robotics RB1
> items:
> - enum:
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260828034958.3165-1-shengchao.guo@oss.qualcomm.com?part=4
next prev parent reply other threads:[~2026-08-28 4:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 3:49 [PATCH v13 0/6] Add initial device trees for Nord platform Shawn Guo
2026-08-28 3:49 ` [PATCH v13 1/6] arm64: dts: qcom: Add device tree for Nord SoC series Shawn Guo
2026-08-28 4:02 ` sashiko-bot
2026-08-28 3:49 ` [PATCH v13 2/6] arm64: dts: qcom: Add device tree for Nord GearVM variant Shawn Guo
2026-08-28 4:00 ` sashiko-bot
2026-08-28 3:49 ` [PATCH v13 3/6] arm64: dts: qcom: Add device tree for Nord Embedded variant Shawn Guo
2026-08-28 3:49 ` [PATCH v13 4/6] dt-bindings: arm: qcom: Document Nord reference boards Shawn Guo
2026-08-28 4:03 ` sashiko-bot [this message]
2026-08-28 3:49 ` [PATCH v13 5/6] arm64: dts: qcom: Add device tree for Nord Ride board Shawn Guo
2026-08-28 9:08 ` Abel Vesa
2026-08-28 3:49 ` [PATCH v13 6/6] arm64: dts: qcom: Add device tree for Nord RRD board Shawn Guo
2026-08-28 9:09 ` 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=20260828040304.0E3161F000E9@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 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.