linux-arm-msm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yijie Yang <yijie.yang@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: arm: qcom: Document HAMOA-IOT-EVK board
Date: Wed, 16 Jul 2025 11:30:26 +0200	[thread overview]
Message-ID: <604a5823-c563-4d37-ab14-e3164f3b1cd8@kernel.org> (raw)
In-Reply-To: <20250716-hamoa_initial-v1-1-f6f5d0f9a163@oss.qualcomm.com>

On 16/07/2025 11:08, Yijie Yang wrote:
> Document the device tree binding for a new board named "EVK" based on
> the Qualcomm Hamoa-IoT platform.
> 
> The "hamoa" name refers to a family of SoCs that share the same silicon
> die but are offered in multiple speed bins. The specific SoC used in
> this board is the x1e80100, which represents one such bin within the
> Hamoa family.
> 
> Although "qcom,hamoa-iot-evk" is introduced as the board-specific
> compatible, the fallback compatible remains "qcom,x1e80100" to preserve
> compatibility with existing in-kernel drivers and software that already
> depend on this identifier.
> 
> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
> ---
>  Documentation/devicetree/bindings/arm/qcom.yaml | 9 +++++++--
>  1 file changed, 7 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> index ae43b35565808ed27cd8354b9a342545c4a98ed6..83b09ec1100ca03044c832212a99e65cc1177985 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> @@ -100,8 +100,8 @@ description: |
>          sm8550
>          sm8650
>          sm8750
> -        x1e78100
> -        x1e80100
> +        x1e78100 # hamoa
> +        x1e80100 # hamoa


Huh? Why, no drop.


>          x1p42100
>  
>    There are many devices in the list below that run the standard ChromeOS
> @@ -1162,6 +1162,11 @@ properties:
>                - qcom,x1p42100-crd
>            - const: qcom,x1p42100
>  
> +      - items:
> +          - enum:
> +              - qcom,hamoa-iot-evk

Don't duplicate entries. Look how this file is organized.


Best regards,
Krzysztof

  reply	other threads:[~2025-07-16  9:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-16  9:08 [PATCH 0/4] Initial support for Qualcomm Hamoa IOT EVK board Yijie Yang
2025-07-16  9:08 ` [PATCH 1/4] dt-bindings: arm: qcom: Document HAMOA-IOT-EVK board Yijie Yang
2025-07-16  9:30   ` Krzysztof Kozlowski [this message]
2025-07-16 10:26     ` Konrad Dybcio
2025-07-16 10:32       ` Krzysztof Kozlowski
2025-07-17  2:14     ` Yijie Yang
2025-07-16  9:08 ` [PATCH 2/4] firmware: qcom: scm: Allow QSEECOM on HAMOA-IOT-EVK Yijie Yang
2025-07-16  9:08 ` [PATCH 3/4] arm64: dts: qcom: Add HAMOA-IOT-SOM platform Yijie Yang
2025-07-17 16:14   ` Stephan Gerhold
2025-07-17 20:10     ` Konrad Dybcio
2025-07-17 20:14       ` Stephan Gerhold
2025-07-23  7:53         ` Yijie Yang
2025-07-18  6:27     ` Yijie Yang
2025-07-17 18:52   ` Dmitry Baryshkov
2025-07-18  6:33     ` Yijie Yang
2025-07-18  9:26       ` Dmitry Baryshkov
2025-07-22 11:09         ` Yijie Yang
2025-07-18  6:40     ` Krzysztof Kozlowski
2025-07-23  6:28   ` Krzysztof Kozlowski
2025-07-23  6:44     ` Yijie Yang
2025-07-23 11:26       ` Dmitry Baryshkov
2025-07-24  0:48         ` Yijie Yang
2025-07-16  9:08 ` [PATCH 4/4] arm64: dts: qcom: Add base HAMOA-IOT-EVK board Yijie Yang
2025-07-17 16:37   ` Stephan Gerhold
2025-07-18  8:19     ` Yijie Yang
2025-07-18  9:27       ` Dmitry Baryshkov
2025-07-18  9:33         ` Stephan Gerhold
2025-07-18 11:46           ` Dmitry Baryshkov
2025-07-17 15:56 ` [PATCH 0/4] Initial support for Qualcomm Hamoa IOT EVK board Rob Herring (Arm)

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=604a5823-c563-4d37-ab14-e3164f3b1cd8@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=yijie.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).