[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <176160465180.73268.9117580201716444313.b4-ty@kernel.org>
Date: Mon, 27 Oct 2025 17:36:50 -0500
From: Bjorn Andersson <andersson@...nel.org>
To: Konrad Dybcio <konradybcio@...nel.org>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
Cc: linux-arm-msm@...r.kernel.org,
devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] arm64: dts: qcom: rename dtsi files for sm6150, x1e80100 and qcs8300
On Tue, 23 Sep 2025 14:01:53 +0300, Dmitry Baryshkov wrote:
> Bjorn said to me that he disliked the conseqeuences of renaming
> qcs615.dtsi to sm6150.dtsi. Let's increase entropy even more and rename
> even more base DTSI files.
>
> Leaving jokes aside. It's not uncommon to see different names for the
> same SoC (or almost same SoC, with no visible differences from the Linux
> side). The platform now known as 'lemans' is a good example, because it
> had been using SA8775P, QCS9100 and QCS9075 in different contexts for
> slightly different modifications. QCS8300 / QCS8275 is another example.
> All such names cause a lot of confusion when somebody tries to follow
> the actual SoC used by the platform.
>
> [...]
Applied, thanks!
[1/3] arm64: dts: qcom: rename qcs8300 to monaco
commit: e50e601ef5b96def44c9ca9685cda6832eb7578e
[2/3] arm64: dts: qcom: rename x1e80100 to hamoa
commit: 8c0b058ab5983a4be6690a76be9b0294853e8e55
[3/3] arm64: dts: qcom: rename sm6150 to talos
commit: 9a5b294dcc21f0b20b586206e5bab9969b4add1c
Best regards,
--
Bjorn Andersson <andersson@...nel.org>
Powered by blists - more mailing lists