arch/arm64/boot/dts/qcom/lemans-auto.dtsi | 104 ------------------- arch/arm64/boot/dts/qcom/sa8775p-ride-r3.dts | 2 +- arch/arm64/boot/dts/qcom/sa8775p-ride.dts | 2 +- 3 files changed, 2 insertions(+), 106 deletions(-) delete mode 100644 arch/arm64/boot/dts/qcom/lemans-auto.dtsi
lemans-auto.dtsi maintains an old "automotive" memory map to support
legacy use cases, which stopped being supported by Qualcomm META build
2 years ago. So there is very unlikely anyone still running it. Remove
the file and update sa8775p-ride boards to include lemans.dtsi directly.
Signed-off-by: Shawn Guo <shengchao.guo@oss.qualcomm.com>
---
arch/arm64/boot/dts/qcom/lemans-auto.dtsi | 104 -------------------
arch/arm64/boot/dts/qcom/sa8775p-ride-r3.dts | 2 +-
arch/arm64/boot/dts/qcom/sa8775p-ride.dts | 2 +-
3 files changed, 2 insertions(+), 106 deletions(-)
delete mode 100644 arch/arm64/boot/dts/qcom/lemans-auto.dtsi
diff --git a/arch/arm64/boot/dts/qcom/lemans-auto.dtsi b/arch/arm64/boot/dts/qcom/lemans-auto.dtsi
deleted file mode 100644
index 8db958d60fd1..000000000000
--- a/arch/arm64/boot/dts/qcom/lemans-auto.dtsi
+++ /dev/null
@@ -1,104 +0,0 @@
-// SPDX-License-Identifier: BSD-3-Clause
-/*
- * Copyright (c) 2023, Linaro Limited
- */
-
-/dts-v1/;
-
-#include "lemans.dtsi"
-
-/delete-node/ &pil_camera_mem;
-/delete-node/ &pil_adsp_mem;
-/delete-node/ &q6_adsp_dtb_mem;
-/delete-node/ &q6_gdsp0_dtb_mem;
-/delete-node/ &pil_gdsp0_mem;
-/delete-node/ &pil_gdsp1_mem;
-/delete-node/ &q6_gdsp1_dtb_mem;
-/delete-node/ &q6_cdsp0_dtb_mem;
-/delete-node/ &pil_cdsp0_mem;
-/delete-node/ &pil_gpu_mem;
-/delete-node/ &pil_cdsp1_mem;
-/delete-node/ &q6_cdsp1_dtb_mem;
-/delete-node/ &pil_cvp_mem;
-/delete-node/ &pil_video_mem;
-/delete-node/ &gunyah_md_mem;
-
-/ {
- reserved-memory {
- #address-cells = <2>;
- #size-cells = <2>;
- ranges;
-
- tz_ffi_mem: tz-ffi@91c00000 {
- compatible = "shared-dma-pool";
- reg = <0x0 0x91c00000 0x0 0x1400000>;
- no-map;
- };
-
- pil_camera_mem: pil-camera@95200000 {
- reg = <0x0 0x95200000 0x0 0x500000>;
- no-map;
- };
-
- pil_adsp_mem: pil-adsp@95c00000 {
- reg = <0x0 0x95c00000 0x0 0x1e00000>;
- no-map;
- };
-
- pil_gdsp0_mem: pil-gdsp0@97b00000 {
- reg = <0x0 0x97b00000 0x0 0x1e00000>;
- no-map;
- };
-
- pil_gdsp1_mem: pil-gdsp1@99900000 {
- reg = <0x0 0x99900000 0x0 0x1e00000>;
- no-map;
- };
-
- pil_cdsp0_mem: pil-cdsp0@9b800000 {
- reg = <0x0 0x9b800000 0x0 0x1e00000>;
- no-map;
- };
-
- pil_gpu_mem: pil-gpu@9d600000 {
- reg = <0x0 0x9d600000 0x0 0x2000>;
- no-map;
- };
-
- pil_cdsp1_mem: pil-cdsp1@9d700000 {
- reg = <0x0 0x9d700000 0x0 0x1e00000>;
- no-map;
- };
-
- pil_cvp_mem: pil-cvp@9f500000 {
- reg = <0x0 0x9f500000 0x0 0x700000>;
- no-map;
- };
-
- pil_video_mem: pil-video@9fc00000 {
- reg = <0x0 0x9fc00000 0x0 0x700000>;
- no-map;
- };
-
- audio_mdf_mem: audio-mdf-region@ae000000 {
- reg = <0x0 0xae000000 0x0 0x1000000>;
- no-map;
- };
-
- hyptz_reserved_mem: hyptz-reserved@beb00000 {
- reg = <0x0 0xbeb00000 0x0 0x11500000>;
- no-map;
- };
-
- trusted_apps_mem: trusted-apps@d1900000 {
- reg = <0x0 0xd1900000 0x0 0x3800000>;
- no-map;
- };
- };
-
- firmware {
- scm {
- memory-region = <&tz_ffi_mem>;
- };
- };
-};
diff --git a/arch/arm64/boot/dts/qcom/sa8775p-ride-r3.dts b/arch/arm64/boot/dts/qcom/sa8775p-ride-r3.dts
index b25f0b2c9410..b33b9c8f0e08 100644
--- a/arch/arm64/boot/dts/qcom/sa8775p-ride-r3.dts
+++ b/arch/arm64/boot/dts/qcom/sa8775p-ride-r3.dts
@@ -5,7 +5,7 @@
/dts-v1/;
-#include "lemans-auto.dtsi"
+#include "lemans.dtsi"
#include "lemans-pmics.dtsi"
#include "lemans-ride-common.dtsi"
diff --git a/arch/arm64/boot/dts/qcom/sa8775p-ride.dts b/arch/arm64/boot/dts/qcom/sa8775p-ride.dts
index 2d9028cd60be..a29be5139554 100644
--- a/arch/arm64/boot/dts/qcom/sa8775p-ride.dts
+++ b/arch/arm64/boot/dts/qcom/sa8775p-ride.dts
@@ -5,7 +5,7 @@
/dts-v1/;
-#include "lemans-auto.dtsi"
+#include "lemans.dtsi"
#include "lemans-pmics.dtsi"
#include "lemans-ride-common.dtsi"
--
2.43.0
On 5/8/26 4:29 AM, Shawn Guo wrote: > lemans-auto.dtsi maintains an old "automotive" memory map to support > legacy use cases, which stopped being supported by Qualcomm META build > 2 years ago. So there is very unlikely anyone still running it. Remove > the file and update sa8775p-ride boards to include lemans.dtsi directly. > > Signed-off-by: Shawn Guo <shengchao.guo@oss.qualcomm.com> > --- > arch/arm64/boot/dts/qcom/lemans-auto.dtsi | 104 ------------------- > arch/arm64/boot/dts/qcom/sa8775p-ride-r3.dts | 2 +- > arch/arm64/boot/dts/qcom/sa8775p-ride.dts | 2 +- So because RIDE is the "automotive development" platform, do we have anyone running the (effectively) IoT firmware on it, or should the boards be removed in general? Konrad
On Fri, May 08, 2026 at 10:35:10AM +0200, Konrad Dybcio wrote: > On 5/8/26 4:29 AM, Shawn Guo wrote: > > lemans-auto.dtsi maintains an old "automotive" memory map to support > > legacy use cases, which stopped being supported by Qualcomm META build > > 2 years ago. So there is very unlikely anyone still running it. Remove > > the file and update sa8775p-ride boards to include lemans.dtsi directly. > > > > Signed-off-by: Shawn Guo <shengchao.guo@oss.qualcomm.com> > > --- > > arch/arm64/boot/dts/qcom/lemans-auto.dtsi | 104 ------------------- > > arch/arm64/boot/dts/qcom/sa8775p-ride-r3.dts | 2 +- > > arch/arm64/boot/dts/qcom/sa8775p-ride.dts | 2 +- > > So because RIDE is the "automotive development" platform, do we have > anyone running the (effectively) IoT firmware on it, or should the > boards be removed in general? I doubt that one can run IoT firmware, i.e. QCS9100 version, directly on SA8775P board, even though both are non-gearvm variant. At least, SA8775P and QCS9100 have different SoC ID. I'm all for removing sa8775p-ride boards if they are completely obsolete and superseded by qcs9100-ride. For the record, I haven't seen sa8775p-ride board anywhere these days. Shawn
© 2016 - 2026 Red Hat, Inc.