Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Aiqun Yu (Maria)" <quic_aiquny@quicinc.com>,
	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: Mon, 19 Aug 2024 13:00:14 +0200	[thread overview]
Message-ID: <9fce86a4-fadd-43cc-ab99-8524a6396d1e@kernel.org> (raw)
In-Reply-To: <2229cc1a-0fa0-4291-874e-43b31f82ef50@quicinc.com>

On 13/08/2024 10:59, Aiqun Yu (Maria) wrote:
>>>>>> 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)?
>>>>>
>>>>> We will support both boards. Sa8775p-ride board with sa8775p chipset and
>>>>> sa8775p-ride board with qcs9100 chipset. Both of them can be used for
>>>>> development.
>>>>
>>>> Patch does something else then - changes compatibles for the existing
>>>> (old) board.
>>>
>>> Can you educate us the right way to add the qcs9100 SoC support in 
>>> sa8775p-ride board? We don't want to duplicate whole device tree file 
>>> since all the hardwares are same except the SoC, so we add qcs9100 SoC 
>>> compatible to sa8775p-ride board and still keep sa8775p SoC compatible.
>>
>> Split board DTS into shared DTSI (just don't forget about proper
>> -M/-C/-B arguments for format-patch) and include it in relevant boards.
>> You also need new SoC DTSI. This will be unusual code, but it matches
>> what you want to achieve.
> 
> If we create two additional DTSs, a total of four DTBs will be generated.
> Should we update the current board DTSs (sa8775p-ride-r3.dts and
> sa8775p-ride.dts) to support the pin-to-pin compatible QCS9100 and
> SA8775p SoCs?

I don't know, I don't have such device. Decision should be based on real
life, real events happening, real products, not on feelings.

> 
> Considering the higher usage of QCS9100 boards in IoT compared to
> SA8775p in automotive for these DTBs, perhaps we should prioritize the
> 'qcom,qcs9100' compatibility before 'qcom,sa8775p'.

Prioritize in what way? What does it mean?

Best regards,
Krzysztof


      reply	other threads:[~2024-08-19 11:00 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
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 [this message]

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=9fce86a4-fadd-43cc-ab99-8524a6396d1e@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_aiquny@quicinc.com \
    --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