From: Caleb Connolly <caleb.connolly@linaro.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
Tengfei Fan <quic_tengfan@quicinc.com>,
Bjorn Andersson <andersson@kernel.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 v2 4/4] arm64: dts: qcom: qcs9100: Add support for the QCS9100 Ride and Ride Rev3 boards
Date: Wed, 8 Jan 2025 15:55:29 +0100 [thread overview]
Message-ID: <fff03f10-7e87-48db-8e8f-b06a47d4545f@linaro.org> (raw)
In-Reply-To: <dc1216db-128f-4cb4-9df9-ba095dfe713d@kernel.org>
On 17/09/2024 01:32, Konrad Dybcio wrote:
> On 11.09.2024 1:10 PM, Tengfei Fan wrote:
>> Add device tree support for the QCS9100 Ride and Ride Rev3 boards. The
>> QCS9100 is a variant of the SA8775p, and they are fully compatible with
>> each other. The QCS9100 Ride/Ride Rev3 board is essentially the same as
>> the SA8775p Ride/Ride Rev3 board, with the QCS9100 SoC mounted instead
>> of the SA8775p.
>>
>> Signed-off-by: Tengfei Fan <quic_tengfan@quicinc.com>
>> ---
>
> Reviewed-by: Konrad Dybcio <konradybcio@kernel.org>
I don't understand this, if both boards are identical except for the
name of the SoC then why do we have two devicetree files?
You can surely detect which SoC is in use at runtime if necessary, and
maybe pick a name which doesn't have the SoC in it if you really want to
avoid confusion.
If there are differentiating features which will be added later, then I
think this at least deserves a comment stating as such.
Additionally, the files should be shuffled around to better represent
that there's two very similar boards with just some minor differences,
this is a common case already and there is a standard way to handle it
(see e.g. sdm845-oneplus-common.dtsi and
sdm845-oneplus-enchilada/fajita.dts)
#include'ing a .dts file just seems like a mess here.
Kind regards,
>
> Konrad
--
// Caleb (they/them)
next prev parent reply other threads:[~2025-01-08 14:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 11:10 [PATCH v2 0/4] arm64: dts: qcom: Add support for the QCS9100 SoC and board Tengfei Fan
2024-09-11 11:10 ` [PATCH v2 1/4] dt-bindings: arm: qcom,ids: add SoC ID for QCS9100 Tengfei Fan
2024-09-11 11:10 ` [PATCH v2 2/4] soc: qcom: socinfo: add QCS9100 ID Tengfei Fan
2024-09-11 11:10 ` [PATCH v2 3/4] dt-bindings: arm: qcom: Document qcs9100-ride and qcs9100-ride Rev3 Tengfei Fan
2024-09-11 11:24 ` Konrad Dybcio
2024-09-16 15:12 ` Krzysztof Kozlowski
2024-09-11 11:10 ` [PATCH v2 4/4] arm64: dts: qcom: qcs9100: Add support for the QCS9100 Ride and Ride Rev3 boards Tengfei Fan
2024-09-16 23:32 ` Konrad Dybcio
2025-01-08 14:55 ` Caleb Connolly [this message]
2024-09-11 13:50 ` [PATCH v2 0/4] arm64: dts: qcom: Add support for the QCS9100 SoC and board Rob Herring (Arm)
2024-11-04 4:13 ` (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=fff03f10-7e87-48db-8e8f-b06a47d4545f@linaro.org \
--to=caleb.connolly@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@quicinc.com \
--cc=konradybcio@kernel.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=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;
as well as URLs for NNTP newsgroup(s).