From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 2/6] ARM: dts: stm32mp: dk1/2: build SCMI-enabled device tree
Date: Mon, 27 Nov 2023 07:40:30 +0100 [thread overview]
Message-ID: <20231127064034.2206788-3-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20231127064034.2206788-1-a.fatoum@pengutronix.de>
Devices with SCMI are booted by the ARM Trusted Firmware-A out of a FIP
bundle. The FIP bundle contains barebox-stm32mp-generic-bl33.img along
with a device tree. Let's build SCMI enabled device trees as well for
the DK1 and DK2, which we already support in non-SCMI mode.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
arch/arm/dts/Makefile | 3 ++-
arch/arm/dts/stm32mp157a-dk1-scmi.dts | 4 ++++
arch/arm/dts/stm32mp157c-dk2-scmi.dts | 4 ++++
3 files changed, 10 insertions(+), 1 deletion(-)
create mode 100644 arch/arm/dts/stm32mp157a-dk1-scmi.dts
create mode 100644 arch/arm/dts/stm32mp157c-dk2-scmi.dts
diff --git a/arch/arm/dts/Makefile b/arch/arm/dts/Makefile
index 339108445afa..37134a32ab0a 100644
--- a/arch/arm/dts/Makefile
+++ b/arch/arm/dts/Makefile
@@ -142,7 +142,8 @@ lwl-$(CONFIG_MACH_SKOV_IMX6) += imx6s-skov-imx6.dtb.o imx6dl-skov-imx6.dtb.o imx
lwl-$(CONFIG_MACH_SKOV_IMX8MP) += imx8mp-skov.dtb.o
lwl-$(CONFIG_MACH_SKOV_ARM9CPU) += at91-skov-arm9cpu.dtb.o
lwl-$(CONFIG_MACH_SEEED_ODYSSEY) += stm32mp157c-odyssey.dtb.o
-lwl-$(CONFIG_MACH_STM32MP15XX_DKX) += stm32mp157c-dk2.dtb.o stm32mp157a-dk1.dtb.o
+lwl-$(CONFIG_MACH_STM32MP15XX_DKX) += stm32mp157c-dk2.dtb.o stm32mp157a-dk1.dtb.o \
+ stm32mp157c-dk2-scmi.dtb.o stm32mp157a-dk1-scmi.dtb.o
lwl-$(CONFIG_MACH_STM32MP13XX_DK) += stm32mp135f-dk.dtb.o
lwl-$(CONFIG_MACH_LXA_MC1) += stm32mp157c-lxa-mc1.dtb.o
lwl-$(CONFIG_MACH_STM32MP15X_EV1) += stm32mp157c-ev1.dtb.o
diff --git a/arch/arm/dts/stm32mp157a-dk1-scmi.dts b/arch/arm/dts/stm32mp157a-dk1-scmi.dts
new file mode 100644
index 000000000000..7092b3af9fe5
--- /dev/null
+++ b/arch/arm/dts/stm32mp157a-dk1-scmi.dts
@@ -0,0 +1,4 @@
+// SPDX-License-Identifier: (GPL-2.0+ OR BSD-3-Clause)
+
+#include <arm/st/stm32mp157a-dk1-scmi.dts>
+#include "stm32mp15xx-dkx.dtsi"
diff --git a/arch/arm/dts/stm32mp157c-dk2-scmi.dts b/arch/arm/dts/stm32mp157c-dk2-scmi.dts
new file mode 100644
index 000000000000..7f015319867a
--- /dev/null
+++ b/arch/arm/dts/stm32mp157c-dk2-scmi.dts
@@ -0,0 +1,4 @@
+// SPDX-License-Identifier: (GPL-2.0+ OR BSD-3-Clause)
+
+#include <arm/st/stm32mp157c-dk2-scmi.dts>
+#include "stm32mp15xx-dkx.dtsi"
--
2.39.2
next prev parent reply other threads:[~2023-11-27 6:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 6:40 [PATCH 0/6] firmware: arm_scmi: add OP-TEE transport support Ahmad Fatoum
2023-11-27 6:40 ` [PATCH 1/6] firmware: arm_scmi: sync with Linux v6.6 Ahmad Fatoum
2023-11-27 6:40 ` Ahmad Fatoum [this message]
2023-11-27 6:40 ` [PATCH 3/6] nvmem: bsec: add support for STM32 bsec pseudo TA Ahmad Fatoum
2023-11-27 6:40 ` [PATCH 4/6] ARM: dts: stm32mp: ev1: build extra device tree with SCMI Ahmad Fatoum
2023-11-27 6:40 ` [PATCH 5/6] ARM: dts: stm32mp: add dtsi for SMC SiP-based SCMI Ahmad Fatoum
2023-11-27 6:40 ` [PATCH 6/6] ARM: dts: stm32mp: lxa-mc1: build SCMI-enabled DT Ahmad Fatoum
2023-12-05 7:29 ` [PATCH 0/6] firmware: arm_scmi: add OP-TEE transport support Sascha Hauer
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=20231127064034.2206788-3-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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