From: Wasim Nazir <quic_wasimn@quicinc.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
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 v5 5/6] arm64: dts: qcom: Add support for QCS9075 Ride & Ride-r3
Date: Thu, 9 Jan 2025 20:33:26 +0530 [thread overview]
Message-ID: <Z3/lA+w7BoazNeWk@hu-wasimn-hyd.qualcomm.com> (raw)
In-Reply-To: <Z3/hmncCDG8OzVkc@hu-wasimn-hyd.qualcomm.com>
On Thu, Jan 09, 2025 at 08:17:54PM +0530, Wasim Nazir wrote:
> On Wed, Jan 08, 2025 at 03:09:09PM +0100, Krzysztof Kozlowski wrote:
> > On 03/01/2025 20:58, Dmitry Baryshkov wrote:
> > >>>>>> Initially, we included the DTS [1] file to avoid duplication. However,
> > >>>>>> based on Krzysztof's previous suggestion [2], we change to this format.
> > >>>>>>
> > >>>>>> Please let us know how to proceed further on this.
> > >>>>>
> > >>>>> Krzysztof asked you to include DTSI files instead of including DTS
> > >>>>> files. Hope this helps.
> > >>>>
> > >>>> Are you suggesting that we should also modify the 9100-ride files to
> > >>>> include DTSI instead of DTS for consistency between QCS9100 and QCS9075?
> > >>>> However, this would result in the duplication of Ethernet nodes in all
> > >>>> the ride board files. Would that be acceptable?
> > >>>
> > >>> git mv foo.dts foo.dtsi
> > >>> echo '#include "foo.dtsi"' > foo.dts
> > >>> git add foo.dts
> > >>> git commit
> > >>>
> > >>
> > >> We cannot convert sa8775p-ride-r3.dts and sa8775p-ride.dts to .dtsi as
> > >> they represent different platforms. In patch [1], we included these DTS
> > >> files to reuse the common hardware nodes.
> > >>
> > >> Could you please advise on how we should proceed with the following
> > >> approaches?
> > >>
> > >> a) Previous approach [1]:
> > >> Include sa8775p-ride-r3.dts and sa8775p-ride.dts in the qcs9075-ride
> > >> platform DTS, similar to the qcs9100-ride platform DTS. This approach
> > >> avoids duplicating Ethernet nodes and maintains uniformity. However, it
> > >> involves including the DTS file directly.
> > >>
> > >> b) Current suggestion:
> > >> Include sa8775p-ride.dtsi in the qcs9075-ride platform DTS and also
> > >> modify the qcs9100-ride platform DTS files to maintain uniformity. This
> > >> approach results in duplicating Ethernet nodes.
> > >>
> > >> Please let us know your recommendation to finalize the DT structure.
> > >
> > > sa8775p.dtsi
> > > `__sa8775p-ride.dtsi
> > > `__sa8775p-ride-r2.dtsi
> > > `__sa8775p-ride.dts
> > > `__qcs9100-ride.dts
> > > `__qcs9075-ride.dts
> > > `__sa8775p-ride-r3.dtsi
> > > `__sa8775p-ride-r3.dts
> > > `__qcs9100-ride-r3.dts
> > > `__qcs9075-ride-r3.dts
> > >
> > Wasim and all other copy-pasters of sa8775p-ride,
> >
> > Just to recap, qcs9100 contributions started this terrible pattern of
> > board including a board. Unfortunately qcs9100 was merged, so that ship
> > has sailed.
> >
> > This patchset was going the same way, because poor choices like to keep
> > spreading, but at one of previous versions I noticed it and objected.
> >
> > This v5 however solves above problem by duplicating the nodes.
> >
> > Apparently all these designs - sa8755p, qcs9100 and qcs9075 - use the
> > same board, but none of this was communicated. I checked all the commit
> > msgs in this patchset and nothing explained about it. What annoys me is
> > that you do not communicate your design forcing us to accept poor DTS or
> > forcing us to guess and make poor judgments.
> >
> > Come with proper hardware description and split out shared parts, like
> > motherboard. Look how other vendors are doing it, e.g. NXP or Renesas.
> > But assuming there are shared parts because I am pretty sure you will
> > pick my comments when it suits you without actually following them fully
> > and without understanding and explaining to us your own hardware.
> >
>
> Hi Krzysztof,
>
> Here is the pictorial flow showing how SoCs are derived and what all boards
> are supported.
>
+-----------------------------------------------------------------------+
| |
| sa8775p |
| | |
| +-----------------------+-----------------------+ |
| | | | |
| v | v |
| qcs9100 | qcs9075 |
| | | | |
| v v v |
| (IOT) (AUTO) (IOT) |
| qcs9100-ride.dts sa8775p-ride.dts qcs9075-ride.dts |
| qcs9100-ride-r3.dts sa8775p-ride-r3.dts qcs9075-ride-r3.dts |
| qcs9075-rb8.dts |
| |
+-----------------------------------------------------------------------+
Updating it as previous one is messed up with whitespaces.
>
> Although we included details about the QCS9075 and QCS9100 in the cover
> letter and commit message, explaining their differences and common
> origin from the SA8775P SOC, the new DT structure suggested by Dmitry
> should make things clearer. This structure properly splits common parts
> and enhances reusability.
>
> > Best regards,
> > Krzysztof
>
> Thanks & Regards,
> Wasim
next prev parent reply other threads:[~2025-01-09 15:03 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-29 15:23 [PATCH v5 0/6] arm64: qcom: Add support for QCS9075 boards Wasim Nazir
2024-12-29 15:23 ` [PATCH v5 1/6] dt-bindings: arm: qcom,ids: add SoC ID for QCS9075 Wasim Nazir
2024-12-29 15:23 ` [PATCH v5 2/6] soc: qcom: socinfo: add QCS9075 SoC ID Wasim Nazir
2024-12-29 15:23 ` [PATCH v5 3/6] dt-bindings: arm: qcom: Document rb8/ride/ride-r3 on QCS9075 Wasim Nazir
2024-12-29 15:23 ` [PATCH v5 4/6] arm64: dts: qcom: Add support for QCS9075 RB8 Wasim Nazir
2025-05-06 12:08 ` Dmitry Baryshkov
2025-05-06 12:29 ` Wasim Nazir
2025-05-06 12:30 ` Dmitry Baryshkov
2025-05-06 13:14 ` Wasim Nazir
2025-05-09 22:56 ` Konrad Dybcio
2024-12-29 15:23 ` [PATCH v5 5/6] arm64: dts: qcom: Add support for QCS9075 Ride & Ride-r3 Wasim Nazir
2024-12-30 15:32 ` Konrad Dybcio
2024-12-31 5:10 ` Andrew Lunn
2025-01-02 9:13 ` Wasim Nazir
2024-12-30 15:45 ` Dmitry Baryshkov
2025-01-02 9:07 ` Wasim Nazir
2025-01-03 5:50 ` Dmitry Baryshkov
2025-01-03 7:07 ` Wasim Nazir
2025-01-03 10:31 ` Dmitry Baryshkov
2025-01-03 18:59 ` Wasim Nazir
2025-01-03 19:58 ` Dmitry Baryshkov
2025-01-08 14:09 ` Krzysztof Kozlowski
2025-01-09 14:47 ` Wasim Nazir
2025-01-09 15:03 ` Wasim Nazir [this message]
2025-01-09 16:16 ` Krzysztof Kozlowski
2025-01-15 5:48 ` Wasim Nazir
2025-01-15 8:35 ` Krzysztof Kozlowski
2025-02-27 7:37 ` Wasim Nazir
2025-03-03 7:46 ` Krzysztof Kozlowski
2025-03-06 8:17 ` Wasim Nazir
2025-03-06 8:25 ` Wasim Nazir
2025-03-11 8:02 ` Krzysztof Kozlowski
2025-03-20 11:45 ` Wasim Nazir
2025-03-29 4:48 ` Krzysztof Kozlowski
2025-04-02 6:48 ` Wasim Nazir
2025-03-11 7:59 ` Krzysztof Kozlowski
2025-01-09 13:52 ` Wasim Nazir
2025-01-06 23:59 ` Bjorn Andersson
2025-01-09 13:36 ` Wasim Nazir
2024-12-29 15:23 ` [PATCH v5 6/6] arm64: dts: qcom: Enable cpu cooling devices for QCS9075 platforms Wasim Nazir
2024-12-30 6:02 ` Aiqun(Maria) Yu
2024-12-30 15:35 ` Konrad Dybcio
2024-12-31 11:05 ` Manaf Meethalavalappu Pallikunhi
2024-12-31 16:21 ` Konrad Dybcio
2025-01-08 12:10 ` Manaf Meethalavalappu Pallikunhi
2024-12-30 15:40 ` Dmitry Baryshkov
2024-12-31 12:01 ` Manaf Meethalavalappu Pallikunhi
2025-01-03 5:51 ` Dmitry Baryshkov
2025-01-08 12:27 ` Manaf Meethalavalappu Pallikunhi
2025-01-08 12:46 ` Dmitry Baryshkov
2025-01-08 16:08 ` Manaf Meethalavalappu Pallikunhi
2025-01-09 14:30 ` Konrad Dybcio
2025-01-09 23:54 ` Dmitry Baryshkov
2025-01-10 12:31 ` Konrad Dybcio
2025-01-13 8:43 ` Dmitry Baryshkov
2025-01-14 19:16 ` Manaf Meethalavalappu Pallikunhi
2025-01-15 8:54 ` Dmitry Baryshkov
2024-12-30 18:17 ` [PATCH v5 0/6] arm64: qcom: Add support for QCS9075 boards Rob Herring (Arm)
2025-01-07 16:38 ` (subset) " Bjorn Andersson
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=Z3/lA+w7BoazNeWk@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=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