From: Patrice Chotard <patrice.chotard@foss.st.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
"Patrice Chotard" <patrice.chotard@foss.st.com>,
"Clément Le Goffic" <clement.legoffic@foss.st.com>
Subject: [PATCH 3/5] arm64: dts: st: add TAMP backup register in stm32mp211.dtsi
Date: Thu, 10 Sep 2026 17:14:26 +0200 [thread overview]
Message-ID: <20260910-upstream_tamp_nvram_dts_part-v1-3-e2bca58a65f4@foss.st.com> (raw)
In-Reply-To: <20260910-upstream_tamp_nvram_dts_part-v1-0-e2bca58a65f4@foss.st.com>
TAMP backup registers allow information sharing between different
software components/execution levels.
They are described individually as nvmem cells.
Signed-off-by: Clément Le Goffic <clement.legoffic@foss.st.com>
Signed-off-by: Patrice Chotard <patrice.chotard@foss.st.com>
---
arch/arm64/boot/dts/st/stm32mp211.dtsi | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/arch/arm64/boot/dts/st/stm32mp211.dtsi b/arch/arm64/boot/dts/st/stm32mp211.dtsi
index 4bfd58b26b51..764a9a3d108e 100644
--- a/arch/arm64/boot/dts/st/stm32mp211.dtsi
+++ b/arch/arm64/boot/dts/st/stm32mp211.dtsi
@@ -133,6 +133,36 @@ syscfg: syscon@44230000 {
reg = <0x44230000 0x0 0x10000>;
};
+ tamp: tamp@46010000 {
+ compatible = "st,stm32-tamp", "syscon", "simple-mfd";
+ #address-cells = <1>;
+ #size-cells = <2>;
+ reg = <0x46010000 0x0 0x400>;
+ ranges;
+
+ nvram: nvram@46010100 {
+ compatible = "st,stm32mp25-tamp-nvram";
+ reg = <0x46010100 0x0 0x200>;
+ nvmem-layout {
+ compatible = "fixed-layout";
+ #address-cells = <1>;
+ #size-cells = <1>;
+
+ boot_mode: tamp-bkp@180 {
+ reg = <0x180 0x4>;
+ };
+
+ rsc_tbl_addr: tamp-bkp@184 {
+ reg = <0x184 0x4>;
+ };
+
+ rsc_tbl_size: tamp-bkp@188 {
+ reg = <0x188 0x4>;
+ };
+ };
+ };
+ };
+
intc: interrupt-controller@4ac10000 {
compatible = "arm,gic-400";
reg = <0x4ac10000 0x0 0x1000>,
--
2.43.0
next prev parent reply other threads:[~2026-09-10 15:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 15:14 [PATCH 0/5] Add STM32 TAMP nvram support Patrice Chotard
2026-09-10 15:14 ` [PATCH 1/5] ARM: dts: stm32: add TAMP backup register in stm32mp131.dtsi Patrice Chotard
2026-09-10 15:29 ` sashiko-bot
2026-09-11 8:17 ` Patrice CHOTARD
2026-09-10 15:14 ` [PATCH 2/5] ARM: dts: stm32: add TAMP backup register in stm32mp151.dtsi Patrice Chotard
2026-09-10 15:26 ` sashiko-bot
2026-09-11 8:18 ` Patrice CHOTARD
2026-09-10 15:14 ` Patrice Chotard [this message]
2026-09-10 15:14 ` [PATCH 4/5] arm64: dts: st: add TAMP backup register in stm32mp231.dtsi Patrice Chotard
2026-09-10 15:14 ` [PATCH 5/5] arm64: dts: st: add TAMP backup register in stm32mp251.dtsi Patrice Chotard
2026-09-10 15:25 ` sashiko-bot
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=20260910-upstream_tamp_nvram_dts_part-v1-3-e2bca58a65f4@foss.st.com \
--to=patrice.chotard@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=clement.legoffic@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.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