Two backup registers are used to store the Cortex-M4 state and the resource
table address.
Declare the tamp node and add associated properties in m4_rproc node
to allow Linux to attach to a firmware loaded by the first boot stages.

Associated driver implementation is available in commit 9276536f455b3
("remoteproc: stm32: Parse syscon that will manage M4 synchronisation").

Signed-off-by: Arnaud Pouliquen <arnaud.pouliq...@st.com>
---
 arch/arm/boot/dts/stm32mp151.dtsi | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/arch/arm/boot/dts/stm32mp151.dtsi 
b/arch/arm/boot/dts/stm32mp151.dtsi
index bfe29023fbd5..842ecffae73a 100644
--- a/arch/arm/boot/dts/stm32mp151.dtsi
+++ b/arch/arm/boot/dts/stm32mp151.dtsi
@@ -1541,6 +1541,11 @@
                        status = "disabled";
                };
 
+               tamp: tamp@5c00a000 {
+                       compatible = "st,stm32-tamp", "syscon";
+                       reg = <0x5c00a000 0x400>;
+               };
+
                /*
                 * Break node order to solve dependency probe issue between
                 * pinctrl and exti.
@@ -1717,6 +1722,8 @@
                        st,syscfg-holdboot = <&rcc 0x10C 0x1>;
                        st,syscfg-tz = <&rcc 0x000 0x1>;
                        st,syscfg-pdds = <&pwr_mcu 0x0 0x1>;
+                       st,syscfg-rsc-tbl = <&tamp 0x144 0xFFFFFFFF>;
+                       st,syscfg-m4-state = <&tamp 0x148 0xFFFFFFFF>;
                        status = "disabled";
                };
        };
-- 
2.17.1

Reply via email to