All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Yuanjie Yang" <yuanjie.yang@oss.qualcomm.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v3 1/4] dt-bindings: arm: qcom: fix PURWA/HAMOA IOT SOM compatibles
Date: Wed, 05 Aug 2026 10:38:49 +0000	[thread overview]
Message-ID: <20260805103850.50EFC1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260805-hamoa-come-v3-v3-1-20463c43eae1@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Critical] Renaming device tree compatible strings in the YAML schema without updating the corresponding device tree (.dts) files breaks schema validation and ABI.
--

--- Patch [1]: [PATCH v3 1/4] dt-bindings: arm: qcom: fix PURWA/HAMOA IOT SOM compatibles ---
commit 86746ff462577b3f827d2ec7f0eb293389e741dc
Author: Yuanjie Yang <yuanjie.yang@oss.qualcomm.com>

dt-bindings: arm: qcom: fix PURWA/HAMOA IOT SOM compatibles

This commit updates the compatible strings for the Hamoa and Purwa IoT
SOM platforms in the device tree bindings. It renames hamoa-iot-som to
iq-x7181-evk-som and purwa-iot-som to iq-x5121-evk-som to match the
official hardware documentation.

> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> index ff8a35df7862d..f244f547d5114 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> @@ -1220,7 +1220,7 @@ properties:
>        - items:
>            - enum:
>                - qcom,hamoa-iot-evk
> -          - const: qcom,hamoa-iot-som
> +          - const: qcom,iq-x7181-evk-som

[Severity: Critical]
Does replacing this compatible string break device tree schema validation for
existing boards?

Since the corresponding device tree files still use the old compatible
string, running make dtbs_check will report that qcom,hamoa-iot-som is
undefined. For example, in arch/arm64/boot/dts/qcom/hamoa-iot-evk.dts:

	compatible = "qcom,hamoa-iot-evk", "qcom,hamoa-iot-som", "qcom,x1e80100";

Also, does removing a deployed compatible string without retaining backwards
compatibility break the device tree ABI for existing bootloaders?

>            - const: qcom,x1e80100
>  
>        - items:

[ ... ]

> @@ -1235,7 +1235,7 @@ properties:
>        - items:
>            - enum:
>                - qcom,purwa-iot-evk
> -          - const: qcom,purwa-iot-som
> +          - const: qcom,iq-x5121-evk-som

[Severity: Critical]
Will replacing this compatible string also break schema validation for the
Purwa IoT EVK board?

Similar to the Hamoa board, arch/arm64/boot/dts/qcom/purwa-iot-evk.dts still
uses the old string:

	compatible = "qcom,purwa-iot-evk", "qcom,purwa-iot-som", "qcom,x1p42100";

>            - const: qcom,x1p42100

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260805-hamoa-come-v3-v3-0-20463c43eae1@oss.qualcomm.com?part=1

  reply	other threads:[~2026-08-05 10:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 10:29 [PATCH v3 0/4] Initial support for Advantech SOM-DB5830 board Yuanjie Yang
2026-08-05 10:30 ` [PATCH v3 1/4] dt-bindings: arm: qcom: fix PURWA/HAMOA IOT SOM compatibles Yuanjie Yang
2026-08-05 10:38   ` sashiko-bot [this message]
2026-08-06  5:52     ` yuanjiey
2026-08-06  8:04   ` Krzysztof Kozlowski
2026-08-06  8:26     ` yuanjiey
2026-08-05 10:30 ` [PATCH v3 2/4] arm64: dts: " Yuanjie Yang
2026-08-05 10:37   ` sashiko-bot
2026-08-05 10:30 ` [PATCH v3 3/4] dt-bindings: arm: qcom: Add Advantech SOM-DB5830 Yuanjie Yang
2026-08-06  8:05   ` Krzysztof Kozlowski
2026-08-05 10:30 ` [PATCH v3 4/4] arm64: dts: " Yuanjie Yang
2026-08-05 13:46   ` 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=20260805103850.50EFC1F000E9@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=yuanjie.yang@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.