[PATCH 0/3] arm64: dts: qcom: rename dtsi files for sm6150, x1e80100 and qcs8300

Dmitry Baryshkov posted 3 patches 1 week, 1 day ago
arch/arm64/boot/dts/qcom/hamoa-iot-som.dtsi                        | 4 ++--
arch/arm64/boot/dts/qcom/{x1e80100-pmics.dtsi => hamoa-pmics.dtsi} | 0
arch/arm64/boot/dts/qcom/{x1e80100.dtsi => hamoa.dtsi}             | 0
arch/arm64/boot/dts/qcom/monaco-evk.dts                            | 4 ++--
arch/arm64/boot/dts/qcom/{qcs8300-pmics.dtsi => monaco-pmics.dtsi} | 0
arch/arm64/boot/dts/qcom/{qcs8300.dtsi => monaco.dtsi}             | 0
arch/arm64/boot/dts/qcom/qcs615-ride.dts                           | 2 +-
arch/arm64/boot/dts/qcom/qcs8300-ride.dts                          | 4 ++--
arch/arm64/boot/dts/qcom/{sm6150.dtsi => talos.dtsi}               | 0
arch/arm64/boot/dts/qcom/x1-asus-zenbook-a14.dtsi                  | 2 +-
arch/arm64/boot/dts/qcom/x1-crd.dtsi                               | 2 +-
arch/arm64/boot/dts/qcom/x1-dell-thena.dtsi                        | 2 +-
arch/arm64/boot/dts/qcom/x1e001de-devkit.dts                       | 4 ++--
arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dtsi        | 4 ++--
arch/arm64/boot/dts/qcom/x1e80100-asus-vivobook-s15.dts            | 4 ++--
arch/arm64/boot/dts/qcom/x1e80100-asus-zenbook-a14.dts             | 2 +-
arch/arm64/boot/dts/qcom/x1e80100-crd.dts                          | 2 +-
arch/arm64/boot/dts/qcom/x1e80100-dell-inspiron-14-plus-7441.dts   | 2 +-
arch/arm64/boot/dts/qcom/x1e80100-dell-latitude-7455.dts           | 2 +-
arch/arm64/boot/dts/qcom/x1e80100-dell-xps13-9345.dts              | 4 ++--
arch/arm64/boot/dts/qcom/x1e80100-hp-omnibook-x14.dts              | 4 ++--
arch/arm64/boot/dts/qcom/x1e80100-lenovo-yoga-slim7x.dts           | 4 ++--
arch/arm64/boot/dts/qcom/x1e80100-microsoft-romulus.dtsi           | 4 ++--
arch/arm64/boot/dts/qcom/x1e80100-qcp.dts                          | 4 ++--
arch/arm64/boot/dts/qcom/x1p42100-hp-omnibook-x14.dts              | 2 +-
arch/arm64/boot/dts/qcom/x1p42100-lenovo-thinkbook-16.dts          | 2 +-
arch/arm64/boot/dts/qcom/x1p42100.dtsi                             | 4 ++--
27 files changed, 34 insertions(+), 34 deletions(-)
[PATCH 0/3] arm64: dts: qcom: rename dtsi files for sm6150, x1e80100 and qcs8300
Posted by Dmitry Baryshkov 1 week, 1 day ago
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.

For 'lemans' after a lot of trial, error, Naks and reviews we've settled
upon having 'lemans.dtsi', the core DT file for the platform and then
naming individual DT files following the marketing name for the platform
or for the SoC.

Apply the same approach to several other platforms, renaming the base
DTSI and keeping the DT names as is.

Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
---
Dmitry Baryshkov (3):
      arm64: dts: qcom: rename qcs8300 to monaco
      arm64: dts: qcom: rename x1e80100 to hamoa
      arm64: dts: qcom: rename sm6150 to talos

 arch/arm64/boot/dts/qcom/hamoa-iot-som.dtsi                        | 4 ++--
 arch/arm64/boot/dts/qcom/{x1e80100-pmics.dtsi => hamoa-pmics.dtsi} | 0
 arch/arm64/boot/dts/qcom/{x1e80100.dtsi => hamoa.dtsi}             | 0
 arch/arm64/boot/dts/qcom/monaco-evk.dts                            | 4 ++--
 arch/arm64/boot/dts/qcom/{qcs8300-pmics.dtsi => monaco-pmics.dtsi} | 0
 arch/arm64/boot/dts/qcom/{qcs8300.dtsi => monaco.dtsi}             | 0
 arch/arm64/boot/dts/qcom/qcs615-ride.dts                           | 2 +-
 arch/arm64/boot/dts/qcom/qcs8300-ride.dts                          | 4 ++--
 arch/arm64/boot/dts/qcom/{sm6150.dtsi => talos.dtsi}               | 0
 arch/arm64/boot/dts/qcom/x1-asus-zenbook-a14.dtsi                  | 2 +-
 arch/arm64/boot/dts/qcom/x1-crd.dtsi                               | 2 +-
 arch/arm64/boot/dts/qcom/x1-dell-thena.dtsi                        | 2 +-
 arch/arm64/boot/dts/qcom/x1e001de-devkit.dts                       | 4 ++--
 arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dtsi        | 4 ++--
 arch/arm64/boot/dts/qcom/x1e80100-asus-vivobook-s15.dts            | 4 ++--
 arch/arm64/boot/dts/qcom/x1e80100-asus-zenbook-a14.dts             | 2 +-
 arch/arm64/boot/dts/qcom/x1e80100-crd.dts                          | 2 +-
 arch/arm64/boot/dts/qcom/x1e80100-dell-inspiron-14-plus-7441.dts   | 2 +-
 arch/arm64/boot/dts/qcom/x1e80100-dell-latitude-7455.dts           | 2 +-
 arch/arm64/boot/dts/qcom/x1e80100-dell-xps13-9345.dts              | 4 ++--
 arch/arm64/boot/dts/qcom/x1e80100-hp-omnibook-x14.dts              | 4 ++--
 arch/arm64/boot/dts/qcom/x1e80100-lenovo-yoga-slim7x.dts           | 4 ++--
 arch/arm64/boot/dts/qcom/x1e80100-microsoft-romulus.dtsi           | 4 ++--
 arch/arm64/boot/dts/qcom/x1e80100-qcp.dts                          | 4 ++--
 arch/arm64/boot/dts/qcom/x1p42100-hp-omnibook-x14.dts              | 2 +-
 arch/arm64/boot/dts/qcom/x1p42100-lenovo-thinkbook-16.dts          | 2 +-
 arch/arm64/boot/dts/qcom/x1p42100.dtsi                             | 4 ++--
 27 files changed, 34 insertions(+), 34 deletions(-)
---
base-commit: bf2602a3cb2381fb1a04bf1c39a290518d2538d1
change-id: 20250923-rename-dts-5d74d6132f40

Best regards,
-- 
With best wishes
Dmitry
Re: [PATCH 0/3] arm64: dts: qcom: rename dtsi files for sm6150, x1e80100 and qcs8300
Posted by Luca Weiss 1 week, 1 day ago
On Tue Sep 23, 2025 at 1:01 PM CEST, 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.
>
> For 'lemans' after a lot of trial, error, Naks and reviews we've settled
> upon having 'lemans.dtsi', the core DT file for the platform and then
> naming individual DT files following the marketing name for the platform
> or for the SoC.
>
> Apply the same approach to several other platforms, renaming the base
> DTSI and keeping the DT names as is.

If we're doing this already, sc7280 -> kodiak? That also covers sc7280,
qc{m,s}6490 & 5430 and sm7325.

Also, does this mean that milos-based Fairphone 6 the dtsi should be
milos.dtsi while dts should be sm7635-fairphone-fp6? The latest patch
series uses milos-fairphone-fp6.dts.

Regards
Luca

>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> ---
> Dmitry Baryshkov (3):
>       arm64: dts: qcom: rename qcs8300 to monaco
>       arm64: dts: qcom: rename x1e80100 to hamoa
>       arm64: dts: qcom: rename sm6150 to talos
>
>  arch/arm64/boot/dts/qcom/hamoa-iot-som.dtsi                        | 4 ++--
>  arch/arm64/boot/dts/qcom/{x1e80100-pmics.dtsi => hamoa-pmics.dtsi} | 0
>  arch/arm64/boot/dts/qcom/{x1e80100.dtsi => hamoa.dtsi}             | 0
>  arch/arm64/boot/dts/qcom/monaco-evk.dts                            | 4 ++--
>  arch/arm64/boot/dts/qcom/{qcs8300-pmics.dtsi => monaco-pmics.dtsi} | 0
>  arch/arm64/boot/dts/qcom/{qcs8300.dtsi => monaco.dtsi}             | 0
>  arch/arm64/boot/dts/qcom/qcs615-ride.dts                           | 2 +-
>  arch/arm64/boot/dts/qcom/qcs8300-ride.dts                          | 4 ++--
>  arch/arm64/boot/dts/qcom/{sm6150.dtsi => talos.dtsi}               | 0
>  arch/arm64/boot/dts/qcom/x1-asus-zenbook-a14.dtsi                  | 2 +-
>  arch/arm64/boot/dts/qcom/x1-crd.dtsi                               | 2 +-
>  arch/arm64/boot/dts/qcom/x1-dell-thena.dtsi                        | 2 +-
>  arch/arm64/boot/dts/qcom/x1e001de-devkit.dts                       | 4 ++--
>  arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dtsi        | 4 ++--
>  arch/arm64/boot/dts/qcom/x1e80100-asus-vivobook-s15.dts            | 4 ++--
>  arch/arm64/boot/dts/qcom/x1e80100-asus-zenbook-a14.dts             | 2 +-
>  arch/arm64/boot/dts/qcom/x1e80100-crd.dts                          | 2 +-
>  arch/arm64/boot/dts/qcom/x1e80100-dell-inspiron-14-plus-7441.dts   | 2 +-
>  arch/arm64/boot/dts/qcom/x1e80100-dell-latitude-7455.dts           | 2 +-
>  arch/arm64/boot/dts/qcom/x1e80100-dell-xps13-9345.dts              | 4 ++--
>  arch/arm64/boot/dts/qcom/x1e80100-hp-omnibook-x14.dts              | 4 ++--
>  arch/arm64/boot/dts/qcom/x1e80100-lenovo-yoga-slim7x.dts           | 4 ++--
>  arch/arm64/boot/dts/qcom/x1e80100-microsoft-romulus.dtsi           | 4 ++--
>  arch/arm64/boot/dts/qcom/x1e80100-qcp.dts                          | 4 ++--
>  arch/arm64/boot/dts/qcom/x1p42100-hp-omnibook-x14.dts              | 2 +-
>  arch/arm64/boot/dts/qcom/x1p42100-lenovo-thinkbook-16.dts          | 2 +-
>  arch/arm64/boot/dts/qcom/x1p42100.dtsi                             | 4 ++--
>  27 files changed, 34 insertions(+), 34 deletions(-)
> ---
> base-commit: bf2602a3cb2381fb1a04bf1c39a290518d2538d1
> change-id: 20250923-rename-dts-5d74d6132f40
>
> Best regards,
Re: [PATCH 0/3] arm64: dts: qcom: rename dtsi files for sm6150, x1e80100 and qcs8300
Posted by Dmitry Baryshkov 1 week, 1 day ago
On Tue, Sep 23, 2025 at 03:00:19PM +0200, Luca Weiss wrote:
> On Tue Sep 23, 2025 at 1:01 PM CEST, 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.
> >
> > For 'lemans' after a lot of trial, error, Naks and reviews we've settled
> > upon having 'lemans.dtsi', the core DT file for the platform and then
> > naming individual DT files following the marketing name for the platform
> > or for the SoC.
> >
> > Apply the same approach to several other platforms, renaming the base
> > DTSI and keeping the DT names as is.
> 
> If we're doing this already, sc7280 -> kodiak? That also covers sc7280,
> qc{m,s}6490 & 5430 and sm7325.

And few other platform names with multiple SoC names per platform.

> 
> Also, does this mean that milos-based Fairphone 6 the dtsi should be
> milos.dtsi while dts should be sm7635-fairphone-fp6? The latest patch
> series uses milos-fairphone-fp6.dts.

I'd leave this to Bjorn's discretion.

> 
> Regards
> Luca
> 
> >
> > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
> > ---
> > Dmitry Baryshkov (3):
> >       arm64: dts: qcom: rename qcs8300 to monaco
> >       arm64: dts: qcom: rename x1e80100 to hamoa
> >       arm64: dts: qcom: rename sm6150 to talos
> >
> >  arch/arm64/boot/dts/qcom/hamoa-iot-som.dtsi                        | 4 ++--
> >  arch/arm64/boot/dts/qcom/{x1e80100-pmics.dtsi => hamoa-pmics.dtsi} | 0
> >  arch/arm64/boot/dts/qcom/{x1e80100.dtsi => hamoa.dtsi}             | 0
> >  arch/arm64/boot/dts/qcom/monaco-evk.dts                            | 4 ++--
> >  arch/arm64/boot/dts/qcom/{qcs8300-pmics.dtsi => monaco-pmics.dtsi} | 0
> >  arch/arm64/boot/dts/qcom/{qcs8300.dtsi => monaco.dtsi}             | 0
> >  arch/arm64/boot/dts/qcom/qcs615-ride.dts                           | 2 +-
> >  arch/arm64/boot/dts/qcom/qcs8300-ride.dts                          | 4 ++--
> >  arch/arm64/boot/dts/qcom/{sm6150.dtsi => talos.dtsi}               | 0
> >  arch/arm64/boot/dts/qcom/x1-asus-zenbook-a14.dtsi                  | 2 +-
> >  arch/arm64/boot/dts/qcom/x1-crd.dtsi                               | 2 +-
> >  arch/arm64/boot/dts/qcom/x1-dell-thena.dtsi                        | 2 +-
> >  arch/arm64/boot/dts/qcom/x1e001de-devkit.dts                       | 4 ++--
> >  arch/arm64/boot/dts/qcom/x1e78100-lenovo-thinkpad-t14s.dtsi        | 4 ++--
> >  arch/arm64/boot/dts/qcom/x1e80100-asus-vivobook-s15.dts            | 4 ++--
> >  arch/arm64/boot/dts/qcom/x1e80100-asus-zenbook-a14.dts             | 2 +-
> >  arch/arm64/boot/dts/qcom/x1e80100-crd.dts                          | 2 +-
> >  arch/arm64/boot/dts/qcom/x1e80100-dell-inspiron-14-plus-7441.dts   | 2 +-
> >  arch/arm64/boot/dts/qcom/x1e80100-dell-latitude-7455.dts           | 2 +-
> >  arch/arm64/boot/dts/qcom/x1e80100-dell-xps13-9345.dts              | 4 ++--
> >  arch/arm64/boot/dts/qcom/x1e80100-hp-omnibook-x14.dts              | 4 ++--
> >  arch/arm64/boot/dts/qcom/x1e80100-lenovo-yoga-slim7x.dts           | 4 ++--
> >  arch/arm64/boot/dts/qcom/x1e80100-microsoft-romulus.dtsi           | 4 ++--
> >  arch/arm64/boot/dts/qcom/x1e80100-qcp.dts                          | 4 ++--
> >  arch/arm64/boot/dts/qcom/x1p42100-hp-omnibook-x14.dts              | 2 +-
> >  arch/arm64/boot/dts/qcom/x1p42100-lenovo-thinkbook-16.dts          | 2 +-
> >  arch/arm64/boot/dts/qcom/x1p42100.dtsi                             | 4 ++--
> >  27 files changed, 34 insertions(+), 34 deletions(-)
> > ---
> > base-commit: bf2602a3cb2381fb1a04bf1c39a290518d2538d1
> > change-id: 20250923-rename-dts-5d74d6132f40
> >
> > Best regards,
> 

-- 
With best wishes
Dmitry
Re: [PATCH 0/3] arm64: dts: qcom: rename dtsi files for sm6150, x1e80100 and qcs8300
Posted by Konrad Dybcio 1 week ago
On 9/23/25 5:17 PM, Dmitry Baryshkov wrote:
> On Tue, Sep 23, 2025 at 03:00:19PM +0200, Luca Weiss wrote:
>> On Tue Sep 23, 2025 at 1:01 PM CEST, 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.
>>>
>>> For 'lemans' after a lot of trial, error, Naks and reviews we've settled
>>> upon having 'lemans.dtsi', the core DT file for the platform and then
>>> naming individual DT files following the marketing name for the platform
>>> or for the SoC.
>>>
>>> Apply the same approach to several other platforms, renaming the base
>>> DTSI and keeping the DT names as is.
>>
>> If we're doing this already, sc7280 -> kodiak? That also covers sc7280,
>> qc{m,s}6490 & 5430 and sm7325.
> 
> And few other platform names with multiple SoC names per platform.
> 
>>
>> Also, does this mean that milos-based Fairphone 6 the dtsi should be
>> milos.dtsi while dts should be sm7635-fairphone-fp6? The latest patch
>> series uses milos-fairphone-fp6.dts.
> 
> I'd leave this to Bjorn's discretion.

I think this only makes sense if milos-nos-sm7635-fairphone-fp6 has
physical differences that stem from the SKU being equipped with a
differently capable SoC (which remains mostly software compatible
otherwise)

Konrad