From: Arnaud Pouliquen <arnaud.pouliquen@st.com>
To: Rob Herring <robh@kernel.org>,
Alexandre Torgue <alexandre.torgue@st.com>
Cc: <devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-remoteproc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Arnaud Pouliquen <arnaud.pouliquen@st.com>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
Ohad Ben-Cohen <ohad@wizery.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH v2 4/4] ARM: dts: stm32: update stm32mp151 for remote proc synchronization support
Date: Wed, 14 Oct 2020 14:54:41 +0200 [thread overview]
Message-ID: <20201014125441.2457-5-arnaud.pouliquen@st.com> (raw)
In-Reply-To: <20201014125441.2457-1-arnaud.pouliquen@st.com>
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.pouliquen@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
next prev parent reply other threads:[~2020-10-14 12:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 12:54 [PATCH v2 0/4] ARM: stm32: add DT properties for remote proc synchronisation Arnaud Pouliquen
2020-10-14 12:54 ` [PATCH v2 1/4] dt-bindings: arm: stm32: Add compatible for syscon tamp node Arnaud Pouliquen
2020-10-14 12:54 ` [PATCH v2 2/4] dt-bindings: remoteproc: stm32_rproc: update for firmware synchronization Arnaud Pouliquen
2020-10-19 20:26 ` Rob Herring
2020-10-14 12:54 ` [PATCH v2 3/4] dt-bindings: remoteproc: stm32_rproc: update syscon descriptions Arnaud Pouliquen
2020-10-19 20:27 ` Rob Herring
2020-10-14 12:54 ` Arnaud Pouliquen [this message]
2020-10-14 16:51 ` [PATCH v2 4/4] ARM: dts: stm32: update stm32mp151 for remote proc synchronization support Mathieu Poirier
2020-10-26 15:49 ` [PATCH v2 0/4] ARM: stm32: add DT properties for remote proc synchronisation Bjorn Andersson
2020-11-17 11:18 ` Alexandre Torgue
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=20201014125441.2457-5-arnaud.pouliquen@st.com \
--to=arnaud.pouliquen@st.com \
--cc=a.fatoum@pengutronix.de \
--cc=alexandre.torgue@st.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mathieu.poirier@linaro.org \
--cc=ohad@wizery.com \
--cc=robh@kernel.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;
as well as URLs for NNTP newsgroup(s).