public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wasim Nazir <quic_wasimn@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <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 v3 5/5] arm64: dts: qcom: Add support for QCS9075 Ride & Ride-r3
Date: Tue, 10 Dec 2024 14:54:22 +0530	[thread overview]
Message-ID: <Z1gIsrWAT3QftC4c@hu-wasimn-hyd.qualcomm.com> (raw)
In-Reply-To: <5782d7c6-1a75-4f15-8942-387742e0ae09@kernel.org>

On Tue, Dec 10, 2024 at 08:25:34AM +0100, Krzysztof Kozlowski wrote:
> On 10/12/2024 00:25, Dmitry Baryshkov wrote:
> >>>>>> 9100 & 9075 are different from “safe” perspective. They differ in
> >>>>>> changes related to thermal which will be added later in devicetree.
> >>>>>
> >>>>> Since this can't be inferred from just looking at the changes, please
> >>>>> make sure to add that to the commit message
> >>>>
> >>>> Any include of other DTS is clear sign something is odd here. Including
> >>>> multiple times without any added nodes is showing these are not real
> >>>> products/boards .
> >>>
> >>> We're adding DTS to reuse the common board changes, with plans to
> >>> include the differences in upcoming patches. To provide more clarity, I
> >>> will include patches in this series to highlight the differences between
> >>> the 9100 and 9075 boards.
> >>
> >> Sure, still do not include DTS. Just like C files don't include C files.
> > 
> > So, is the solution simple, rename .dts to .dtsi and include it from
> > both .dts files?
> 
> For example. This leads to more questions - what is common here? We do
> not create shared DTSI files just because someone wants, but to really
> note shared components or shared designs.
> 

We can reuse the common dtsi for ride boards, i.e., sa8775p-ride.dtsi,
and then add board-specific changes in the corresponding files.

If this approach is acceptable, I can proceed with sending the
next patch series. I hope this will help clarify things further.

> Best regards,
> Krzysztof

Thanks & Regards,
Wasim

  reply	other threads:[~2024-12-10  9:24 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-19 17:49 [PATCH v3 0/5] arm64: qcom: Add support for QCS9075 boards Wasim Nazir
2024-11-19 17:49 ` [PATCH v3 1/5] dt-bindings: arm: qcom,ids: add SoC ID for QCS9075 Wasim Nazir
2024-11-19 17:49 ` [PATCH v3 2/5] soc: qcom: socinfo: add QCS9075 SoC ID Wasim Nazir
2024-11-19 17:49 ` [PATCH v3 3/5] dt-bindings: arm: qcom: Document rb8/ride/ride-r3 on QCS9075 Wasim Nazir
2024-11-20 16:43   ` Krzysztof Kozlowski
2024-12-06 11:00     ` Wasim Nazir
2024-11-19 17:49 ` [PATCH v3 4/5] arm64: dts: qcom: Add support for QCS9075 RB8 Wasim Nazir
2024-11-20 11:51   ` Dmitry Baryshkov
2024-12-13 23:52   ` Konrad Dybcio
2024-11-19 17:49 ` [PATCH v3 5/5] arm64: dts: qcom: Add support for QCS9075 Ride & Ride-r3 Wasim Nazir
2024-11-20 11:52   ` Dmitry Baryshkov
2024-11-20 16:44   ` Krzysztof Kozlowski
2024-12-06 11:04     ` Wasim Nazir
2024-12-06 12:14       ` Konrad Dybcio
2024-12-06 12:49         ` Krzysztof Kozlowski
2024-12-09 18:58           ` Wasim Nazir
2024-12-09 19:30             ` Krzysztof Kozlowski
2024-12-09 23:25               ` Dmitry Baryshkov
2024-12-10  7:25                 ` Krzysztof Kozlowski
2024-12-10  9:24                   ` Wasim Nazir [this message]
2024-12-10 11:50                     ` Krzysztof Kozlowski
2024-12-10 14:02                       ` Wasim Nazir
2024-12-09 18:38         ` Wasim Nazir
2024-11-20 16:02 ` [PATCH v3 0/5] arm64: qcom: Add support for QCS9075 boards Rob Herring (Arm)
2024-11-20 16:41 ` Krzysztof Kozlowski
2024-12-06 10:43   ` Wasim Nazir
2024-12-08 17:46     ` Dmitry Baryshkov
2024-12-09 18: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=Z1gIsrWAT3QftC4c@hu-wasimn-hyd.qualcomm.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@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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