From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Jingyi Wang <quic_jingyw@quicinc.com>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, andersson@kernel.org,
konrad.dybcio@linaro.org, robh@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org
Cc: kernel@quicinc.com
Subject: Re: [RFC PATCH 1/6] dt-bindings: arm: qcom: Document sm8650p soc and AIM500 AIoT board
Date: Mon, 5 Feb 2024 13:33:54 +0100 [thread overview]
Message-ID: <2fa4d857-7262-40df-a842-56945ecffb81@linaro.org> (raw)
In-Reply-To: <20240205115721.1195336-2-quic_jingyw@quicinc.com>
On 05/02/2024 12:57, Jingyi Wang wrote:
> Document Qualcomm SM8650P SoC and AIM500 AIoT board.
Please describe shortly what is SM8650P and what are the differences
with SM8650.
>
> Signed-off-by: Jingyi Wang <quic_jingyw@quicinc.com>
> ---
> Documentation/devicetree/bindings/arm/qcom.yaml | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> index 1999a5f2f254..e87ceb42853b 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> @@ -88,11 +88,13 @@ description: |
> sm8450
> sm8550
> sm8650
> + sm8650p
> x1e80100
>
> The 'board' element must be one of the following strings:
>
> adp
> + aim500-aiot
Drop this line.
> cdp
> dragonboard
> idp
> @@ -1051,6 +1053,13 @@ properties:
> - qcom,sm8650-qrd
> - const: qcom,sm8650
>
> + - items:
> + - enum:
> + - qcom,sm8650p-aim500-aiot
> + - const: qcom,sm8650p-aim500
> + - const: qcom,sm8650p
> + - const: qcom,sm8650
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-02-05 12:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 11:57 [RFC PATCH 0/6] arm64: dts: qcom: Introduce AIM500 platform device tree Jingyi Wang
2024-02-05 11:57 ` [RFC PATCH 1/6] dt-bindings: arm: qcom: Document sm8650p soc and AIM500 AIoT board Jingyi Wang
2024-02-05 12:33 ` Krzysztof Kozlowski [this message]
2024-02-20 8:55 ` Jingyi Wang
2024-02-20 9:06 ` Dmitry Baryshkov
2024-02-20 9:31 ` Jingyi Wang
2024-02-20 9:43 ` Krzysztof Kozlowski
2024-02-20 9:46 ` Jingyi Wang
2024-02-05 11:57 ` [RFC PATCH 2/6] dt-bindings: arm: qcom,ids: Add SoC ID for SM8650P Jingyi Wang
2024-02-05 12:34 ` Krzysztof Kozlowski
2024-02-05 11:57 ` [RFC PATCH 3/6] soc: qcom: socinfo: Add SM8650P SoC ID table entry Jingyi Wang
2024-02-05 12:34 ` Krzysztof Kozlowski
2024-02-05 11:57 ` [RFC PATCH 4/6] arm64: dts: qcom: sm8650p: introduce sm8650p dtsi Jingyi Wang
2024-02-22 13:21 ` neil.armstrong
2024-02-23 9:10 ` Aiqun Yu (Maria)
2024-02-05 11:57 ` [RFC PATCH 5/6] arm64: dts: qcom: add base AIM500 dtsi Jingyi Wang
2024-02-05 12:35 ` Krzysztof Kozlowski
2024-02-20 9:11 ` Jingyi Wang
2024-02-20 9:44 ` Krzysztof Kozlowski
2024-02-05 14:23 ` Dmitry Baryshkov
2024-02-20 9:16 ` Jingyi Wang
2024-02-20 9:19 ` Dmitry Baryshkov
2024-02-20 10:06 ` Jingyi Wang
2024-02-20 10:28 ` Aiqun Yu (Maria)
2024-02-05 11:57 ` [RFC PATCH 6/6] arm64: dts: qcom: add AIM500 AIoT Jingyi Wang
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=2fa4d857-7262-40df-a842-56945ecffb81@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@quicinc.com \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_jingyw@quicinc.com \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®