From: Hariharan K <quic_harihk@quicinc.com>
To: Bjorn Andersson <andersson@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: <agross@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>,
<quic_srichara@quicinc.com>, <quic_sjaganat@quicinc.com>,
<quic_kathirav@quicinc.com>, <quic_arajkuma@quicinc.com>,
<quic_anusha@quicinc.com>
Subject: Re: [PATCH 1/2] dt-bindings: arm: qcom: document MI04.1 board based on IPQ5332 family
Date: Wed, 14 Jun 2023 16:10:00 +0530 [thread overview]
Message-ID: <9b13814e-fa3a-9e81-e444-93b566b3cb53@quicinc.com> (raw)
In-Reply-To: <20230613230416.flhnzaiuy4imzs2z@ripper>
On 6/14/2023 4:34 AM, Bjorn Andersson wrote:
> On Tue, Jun 06, 2023 at 01:28:27PM +0200, Krzysztof Kozlowski wrote:
>> On 06/06/2023 11:57, Hariharan K wrote:
>>> Document the MI04.1 (Reference Design Platform 446) board based on IPQ5332
>>> family of SoCs.
>>>
>>> Signed-off-by: Hariharan K <quic_harihk@quicinc.com>
>>> ---
>>> Documentation/devicetree/bindings/arm/qcom.yaml | 2 ++
>>> 1 file changed, 2 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
>>> index 8302d1ee280d..165a815337f7 100644
>>> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
>>> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
>>> @@ -93,6 +93,7 @@ description: |
>>> ap-mi01.2
>>> ap-mi01.3
>>> ap-mi01.6
>>> + ap-mi04.1
>>
>> I think we need to stop adding them here... This was supposed to be
>> limited list for Qualcomm bootloader. Are you sure Qualcomm bootloader
>> requires such names with versions?
>>
>
> Hariharan, can you please elaborate on what these numbers mean? Is this
> just a version of ap-mi04? Or do we have 5 different reference boards on
> IPQ5332, just with "cryptic" names?
>
> Regards,
> Bjorn
Yes. These are different reference board designs based on IPQ5332.
Thanks,
Hariharan K
next prev parent reply other threads:[~2023-06-14 10:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 9:57 [PATCH 0/2] Add initial support for RDP446 of IPQ5332 family Hariharan K
2023-06-06 9:57 ` [PATCH 1/2] dt-bindings: arm: qcom: document MI04.1 board based on " Hariharan K
2023-06-06 11:28 ` Krzysztof Kozlowski
2023-06-13 23:04 ` Bjorn Andersson
2023-06-14 10:40 ` Hariharan K [this message]
2023-06-06 9:57 ` [PATCH 2/2] arm64: dts: qcom: ipq5332: add support for the RDP446 variant Hariharan K
2023-06-14 10:43 ` Konrad Dybcio
2023-06-14 10:59 ` Hariharan K
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=9b13814e-fa3a-9e81-e444-93b566b3cb53@quicinc.com \
--to=quic_harihk@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_anusha@quicinc.com \
--cc=quic_arajkuma@quicinc.com \
--cc=quic_kathirav@quicinc.com \
--cc=quic_sjaganat@quicinc.com \
--cc=quic_srichara@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;
as well as URLs for NNTP newsgroup(s).