From: Krzysztof Kozlowski <krzk@kernel.org>
To: Tingwei Zhang <quic_tingweiz@quicinc.com>,
Tengfei Fan <quic_tengfan@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: kernel@quicinc.com, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] arm64: dts: qcom: sa8775p-ride: Add QCS9100 compatible
Date: Thu, 8 Aug 2024 13:05:03 +0200 [thread overview]
Message-ID: <9323127a-e6b5-4835-afa0-4ce0086fd9d1@kernel.org> (raw)
In-Reply-To: <ace5b3e1-f4a2-4c04-821a-e797d0f55cae@quicinc.com>
On 07/08/2024 13:04, Tingwei Zhang wrote:
> On 8/7/2024 5:35 PM, Krzysztof Kozlowski wrote:
>> On 07/08/2024 11:17, Tengfei Fan wrote:
>>>
>>>
>>> On 8/7/2024 3:28 PM, Krzysztof Kozlowski wrote:
>>>> On 06/08/2024 06:19, Tengfei Fan wrote:
>>>>> Add QCS9100 compatible in sa8775p ride and sa8775p ride r3 board DTS.
>>>>> QCS9100 references SA8775p, they share the same SoC DTSI and board DTS.
>>>>>
>>>>
>>>> I don't understand this. You claim here that QCS9100 references SA8775p
>>>> but your diff says other way: SA8775p references QCS9100.
>>>>
>>>> Sorry, that's confusing.
>>>>
>>>> Best regards,
>>>> Krzysztof
>>>>
>>>
>>> I will update the compatible as follows to indicate that QCS9100
>>> references SA8775p.
>>>
>>> compatible = "qcom,sa8775p-ride", "qcom,qcs9100", "qcom,sa8775p";
>>
>> Is this still correct, though? sa8775p won't come with qcs9100 SoC.
> We have a new board. Hardware is same as sa877p-ride except sa8775p is
> replaced with qcs9100. We add qcs9100 SoC compatible to sa8775p-ride
Does "new board" mean that "old board" disappears? No users to care
about it? Or just the existing board is being changed (like new revision)?
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-08 11:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 4:19 [PATCH 0/4] soc: qcom: Add QCS9100 SoC ID and compatible support Tengfei Fan
2024-08-06 4:19 ` [PATCH 1/4] dt-bindings: arm: qcom,ids: add SoC ID for QCS9100 Tengfei Fan
2024-08-07 7:26 ` Krzysztof Kozlowski
2024-08-06 4:19 ` [PATCH 2/4] soc: qcom: socinfo: add QCS9100 ID Tengfei Fan
2024-08-07 7:26 ` Krzysztof Kozlowski
2024-08-06 4:19 ` [PATCH 3/4] dt-bindings: arm: qcom: Document QCS9100 compatible Tengfei Fan
2024-08-07 7:27 ` Krzysztof Kozlowski
2024-08-07 9:14 ` Tengfei Fan
2024-08-06 4:19 ` [PATCH 4/4] arm64: dts: qcom: sa8775p-ride: Add " Tengfei Fan
2024-08-07 7:28 ` Krzysztof Kozlowski
2024-08-07 9:17 ` Tengfei Fan
2024-08-07 9:35 ` Krzysztof Kozlowski
2024-08-07 11:04 ` Tingwei Zhang
2024-08-08 11:05 ` Krzysztof Kozlowski [this message]
2024-08-12 2:16 ` Tingwei Zhang
2024-08-12 6:15 ` Krzysztof Kozlowski
2024-08-12 7:07 ` Tingwei Zhang
2024-08-13 8:34 ` Krzysztof Kozlowski
2024-08-13 8:59 ` Aiqun Yu (Maria)
2024-08-19 11:00 ` Krzysztof Kozlowski
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=9323127a-e6b5-4835-afa0-4ce0086fd9d1@kernel.org \
--to=krzk@kernel.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=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_tengfan@quicinc.com \
--cc=quic_tingweiz@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