From: Wasim Nazir <quic_wasimn@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: <andersson@kernel.org>, <konrad.dybcio@linaro.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<conor+dt@kernel.org>, <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: Tue, 27 Feb 2024 12:22:29 +0530 [thread overview]
Message-ID: <96733f86-c3dc-4f9d-88a5-654584b5acdf@quicinc.com> (raw)
In-Reply-To: <CAA8EJpqARMwKhybgsFDKNZ=-uSAY=j4ocdZ=ax5U1KVPNXBTCg@mail.gmail.com>
On 2/2/2024 8:21 PM, Dmitry Baryshkov wrote:
> On Fri, 2 Feb 2024 at 15:37, Wasim Nazir <quic_wasimn@quicinc.com> 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.
>
> What is the actual marketing name for the SoM and the carrier board?
> The RB5gen2-HDK doesn't follow the previous example of the RB* boards
> and doesn't sound in tune with the RB3gen2 submission.
> Could you please sync up internally and come up with two similar names
> for the platforms with similar purpose?
>
Discussed internally and we concluded on these official names, will
update accordingly in next patch.
SOM: qcs8550-rb5gen2-som.dtsi
Board: qcs8550-rb5gen2.dts
>>
>> 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
>> ride
>> sbc
>> x100
>> @@ -915,6 +916,14 @@ properties:
>> - const: qcom,qcm8550
>> - const: qcom,sm8550
>>
>> + - items:
>> + - enum:
>> + - qcom,qcs8550-rb5gen2-hdk
>> + - const: qcom,qcs8550-rb5gen2
>> + - const: qcom,qcs8550
>> + - const: qcom,qcm8550
>> + - const: qcom,sm8550
>> +
>> - items:
>> - enum:
>> - qcom,sa8155p-adp
>> --
>> 2.43.0
>>
>>
>
>
Thanks & Regards,
Wasim
next prev parent reply other threads:[~2024-02-27 6:52 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
2024-02-27 6:46 ` Wasim Nazir
2024-02-02 14:51 ` Dmitry Baryshkov
2024-02-27 6:52 ` Wasim Nazir [this message]
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=96733f86-c3dc-4f9d-88a5-654584b5acdf@quicinc.com \
--to=quic_wasimn@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.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=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
all inboxes | Powered by JetHome®