From: sashiko-bot@kernel.org
To: "Komal Bajaj" <komal.bajaj@oss.qualcomm.com>
Cc: robh@kernel.org, conor+dt@kernel.org, olteanv@gmail.com,
devicetree@vger.kernel.org, linux-phy@lists.infradead.org,
neil.armstrong@linaro.org, vkoul@kernel.org
Subject: Re: [PATCH v2 1/5] dt-bindings: arm: qcom: Document Shikra and its EVK boards
Date: Tue, 19 May 2026 11:32:34 +0000 [thread overview]
Message-ID: <20260519113234.BA75FC2BCB3@smtp.kernel.org> (raw)
In-Reply-To: <20260519-shikra-dt-v2-1-c01b90fb4395@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] Device tree compatible strings use generic abbreviations instead of specific hardware part numbers.
- [Low] Alphabetical sorting violation in qcom.yaml.
--
commit d5de85f1dcdd73430dd4bed54ebebe0837ba7f5e
Author: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
dt-bindings: arm: qcom: Document Shikra and its EVK boards
This commit introduces compatible strings for the Qualcomm Shikra SoC in
System-on-Module (SoM) form factors and their corresponding EVK carrier
boards.
> Add compatible strings for the CQ2390M, CQ2390S, IQ2390S SoM variant and its
> corresponding EVK boards.
Should these compatible strings use the specific hardware part numbers
(CQ2390M, CQ2390S, IQ2390S) instead of generic abbreviations like
qcom,shikra-cqm-som?
If the generic abbreviations are kept, can the schema map these
abbreviations to the specific part numbers to document the ABI?
> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> index af266d584fae6..7c5c5f4fc30f7 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> @@ -968,6 +968,24 @@ properties:
> - const: qcom,qcs9100
> - const: qcom,sa8775p
>
> + - items:
> + - enum:
> + - qcom,shikra-cqm-evk
> + - const: qcom,shikra-cqm-som
> + - const: qcom,shikra
This isn't a bug, but should these new blocks be sorted alphabetically
based on the root SoC compatible string?
Since 'h' comes after 'd', could qcom,shikra be placed after qcom,sdm845
instead of after qcom,sa8775p?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260519-shikra-dt-v2-0-c01b90fb4395@oss.qualcomm.com?part=1
WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Komal Bajaj" <komal.bajaj@oss.qualcomm.com>
Cc: robh@kernel.org, conor+dt@kernel.org, olteanv@gmail.com,
devicetree@vger.kernel.org, linux-phy@lists.infradead.org,
neil.armstrong@linaro.org, vkoul@kernel.org
Subject: Re: [PATCH v2 1/5] dt-bindings: arm: qcom: Document Shikra and its EVK boards
Date: Tue, 19 May 2026 11:32:34 +0000 [thread overview]
Message-ID: <20260519113234.BA75FC2BCB3@smtp.kernel.org> (raw)
In-Reply-To: <20260519-shikra-dt-v2-1-c01b90fb4395@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] Device tree compatible strings use generic abbreviations instead of specific hardware part numbers.
- [Low] Alphabetical sorting violation in qcom.yaml.
--
commit d5de85f1dcdd73430dd4bed54ebebe0837ba7f5e
Author: Komal Bajaj <komal.bajaj@oss.qualcomm.com>
dt-bindings: arm: qcom: Document Shikra and its EVK boards
This commit introduces compatible strings for the Qualcomm Shikra SoC in
System-on-Module (SoM) form factors and their corresponding EVK carrier
boards.
> Add compatible strings for the CQ2390M, CQ2390S, IQ2390S SoM variant and its
> corresponding EVK boards.
Should these compatible strings use the specific hardware part numbers
(CQ2390M, CQ2390S, IQ2390S) instead of generic abbreviations like
qcom,shikra-cqm-som?
If the generic abbreviations are kept, can the schema map these
abbreviations to the specific part numbers to document the ABI?
> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> index af266d584fae6..7c5c5f4fc30f7 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> @@ -968,6 +968,24 @@ properties:
> - const: qcom,qcs9100
> - const: qcom,sa8775p
>
> + - items:
> + - enum:
> + - qcom,shikra-cqm-evk
> + - const: qcom,shikra-cqm-som
> + - const: qcom,shikra
This isn't a bug, but should these new blocks be sorted alphabetically
based on the root SoC compatible string?
Since 'h' comes after 'd', could qcom,shikra be placed after qcom,sdm845
instead of after qcom,sa8775p?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260519-shikra-dt-v2-0-c01b90fb4395@oss.qualcomm.com?part=1
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-05-19 11:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-19 11:21 [PATCH v2 0/5] arm64: dts: qcom: Add initial device tree support for Shikra Komal Bajaj
2026-05-19 11:21 ` Komal Bajaj
2026-05-19 11:21 ` [PATCH v2 1/5] dt-bindings: arm: qcom: Document Shikra and its EVK boards Komal Bajaj
2026-05-19 11:21 ` Komal Bajaj
2026-05-19 11:32 ` sashiko-bot [this message]
2026-05-19 11:32 ` sashiko-bot
2026-05-21 13:33 ` Komal Bajaj
2026-05-21 13:33 ` Komal Bajaj
2026-05-19 11:21 ` [PATCH v2 2/5] arm64: dts: qcom: Introduce Shikra SoC base dtsi Komal Bajaj
2026-05-19 11:21 ` Komal Bajaj
2026-05-19 11:47 ` sashiko-bot
2026-05-19 11:47 ` sashiko-bot
2026-05-22 13:33 ` Komal Bajaj
2026-05-22 13:33 ` Komal Bajaj
2026-05-19 11:21 ` [PATCH v2 3/5] arm64: dts: qcom: Add Shikra CQ7790M SoM platform Komal Bajaj
2026-05-19 11:21 ` Komal Bajaj
2026-05-19 11:51 ` Konrad Dybcio
2026-05-19 11:51 ` Konrad Dybcio
2026-05-22 14:29 ` Komal Bajaj
2026-05-22 14:29 ` Komal Bajaj
2026-05-19 12:02 ` sashiko-bot
2026-05-19 12:02 ` sashiko-bot
2026-05-22 14:27 ` Komal Bajaj
2026-05-22 14:27 ` Komal Bajaj
2026-05-19 11:21 ` [PATCH v2 4/5] arm64: dts: qcom: Add Shikra IQ2390S " Komal Bajaj
2026-05-19 11:21 ` Komal Bajaj
2026-05-19 11:21 ` [PATCH v2 5/5] arm64: dts: qcom: Add Shikra EVK boards Komal Bajaj
2026-05-19 11:21 ` Komal Bajaj
2026-05-19 12:37 ` sashiko-bot
2026-05-19 12:37 ` sashiko-bot
2026-05-22 17:52 ` Komal Bajaj
2026-05-22 17:52 ` Komal Bajaj
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=20260519113234.BA75FC2BCB3@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=komal.bajaj@oss.qualcomm.com \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=olteanv@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=vkoul@kernel.org \
/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.