From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Wasim Nazir <quic_wasimn@quicinc.com>,
andersson@kernel.org, konrad.dybcio@linaro.org,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@quicinc.com
Subject: Re: [PATCH 1/3] dt-bindings: arm: qcom: Document rb5gen2-hdk board
Date: Fri, 2 Feb 2024 15:34:19 +0100 [thread overview]
Message-ID: <c9dcbb3b-90eb-4e41-93cf-859d74cf57ea@linaro.org> (raw)
In-Reply-To: <20240202133638.4720-2-quic_wasimn@quicinc.com>
On 02/02/2024 14:36, Wasim Nazir wrote:
> Document board bindings for Rb5 gen2 hardware development kit.
> Rb5gen2-HDK is using Rb5 gen2 SOM which is based on QCS8550 SoC.
> RB5gen2-HDK is development kit used for IOT solutions.
>
> Signed-off-by: Wasim Nazir <quic_wasimn@quicinc.com>
>
> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> index 9cee874a8eae..ce5b5dfe0e46 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> @@ -104,6 +104,7 @@ description: |
> qcp
> qrd
> rb2
> + rb5gen2-hdk
I think we decided to stop growing this, especially that "rb5gen2-hdk"
does not look generic type of a board.
> --
> 2.43.0
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-02-02 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 13:36 [PATCH 0/3] arm64: qcom: add support for QCS8550 RB5gen2 HDK board Wasim Nazir
2024-02-02 13:36 ` [PATCH 1/3] dt-bindings: arm: qcom: Document rb5gen2-hdk board Wasim Nazir
2024-02-02 14:34 ` Krzysztof Kozlowski [this message]
2024-02-27 6:46 ` Wasim Nazir
2024-02-02 14:51 ` Dmitry Baryshkov
2024-02-27 6:52 ` Wasim Nazir
2024-02-02 13:36 ` [PATCH 2/3] arm64: dts: qcom: Add initial support for rb5gen2 SOM Wasim Nazir
2024-02-02 13:36 ` [PATCH 3/3] arm64: dts: qcom: Add initial support for rb5gen2 HDK board Wasim Nazir
2024-02-02 14:53 ` Dmitry Baryshkov
2024-02-27 9:37 ` Wasim Nazir
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=c9dcbb3b-90eb-4e41-93cf-859d74cf57ea@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_wasimn@quicinc.com \
--cc=robh+dt@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