From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 5/6] ARM: dts: stm32mp: add dtsi for SMC SiP-based SCMI
Date: Mon, 27 Nov 2023 07:40:33 +0100 [thread overview]
Message-ID: <20231127064034.2206788-6-a.fatoum@pengutronix.de> (raw)
In-Reply-To: <20231127064034.2206788-1-a.fatoum@pengutronix.de>
Upstream device trees use OP-TEE shared memory for SCMI, but upstream
OP-TEE also supports a compatibility mode to service SCMI over the
a sillicon provider secure monitor call, like what TF-A implements.
This can be enabled via including the device tree added here
and configuring OP-TEE appropriately:
CFG_STM32MP1_SCMI_SIP=y
CFG_STM32MP1_SCMI_SHM_SYSRAM=y
or just compiling TF-A with `AARCH32_SP=sp_min`.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
arch/arm/dts/stm32mp1-scmi-smc.dtsi | 49 +++++++++++++++++++++++++++++
1 file changed, 49 insertions(+)
create mode 100644 arch/arm/dts/stm32mp1-scmi-smc.dtsi
diff --git a/arch/arm/dts/stm32mp1-scmi-smc.dtsi b/arch/arm/dts/stm32mp1-scmi-smc.dtsi
new file mode 100644
index 000000000000..590df657e907
--- /dev/null
+++ b/arch/arm/dts/stm32mp1-scmi-smc.dtsi
@@ -0,0 +1,49 @@
+/* SPDX-License-Identifier: (GPL-2.0+ OR BSD-3-Clause) */
+
+/ {
+ firmware {
+ scmi: scmi {
+ compatible = "arm,scmi-smc";
+ shmem = <&scmi0_shm>;
+ arm,smc-id = <0x82002000>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ scmi_clk: protocol@14 {
+ reg = <0x14>;
+ #clock-cells = <1>;
+ };
+
+ scmi_reset: protocol@16 {
+ reg = <0x16>;
+ #reset-cells = <1>;
+ };
+ };
+ };
+
+ soc {
+ sram@2ffff000 {
+ compatible = "mmio-sram";
+ reg = <0x2ffff000 0x1000>;
+ #address-cells = <1>;
+ #size-cells = <1>;
+ ranges = <0 0x2ffff000 0x1000>;
+
+ scmi0_shm: scmi_shm@0 {
+ compatible = "arm,scmi-shmem";
+ reg = <0 0x80>;
+ };
+
+ scmi1_shm: scmi_shm@200 {
+ compatible = "arm,scmi-shmem";
+ reg = <0x200 0x80>;
+ };
+ };
+ };
+};
+
+/delete-node/ &clk_hse;
+/delete-node/ &clk_hsi;
+/delete-node/ &clk_lse;
+/delete-node/ &clk_lsi;
+/delete-node/ &clk_csi;
--
2.39.2
next prev parent reply other threads:[~2023-11-27 6:41 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 ` [PATCH 2/6] ARM: dts: stm32mp: dk1/2: build SCMI-enabled device tree Ahmad Fatoum
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 ` Ahmad Fatoum [this message]
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-6-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