mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Patrice CHOTARD <patrice.chotard@foss.st.com>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
	<linux-kernel@vger.kernel.org>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
	<devicetree@vger.kernel.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	<linux-amarula@amarulasolutions.com>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [Linux-stm32] [PATCH 2/2] arm64: dts: st: add TAMP-NVRAM support for STM32MP25
Date: Fri, 9 Jan 2026 11:40:21 +0100	[thread overview]
Message-ID: <58006bf6-425a-4016-996b-4a01fdb22cea@foss.st.com> (raw)
In-Reply-To: <20260107194541.1843999-2-dario.binacchi@amarulasolutions.com>



On 1/7/26 20:45, Dario Binacchi wrote:
> Add the TAMP node along with its NVRAM child node and define the
> fixed-layout for fwu_info and boot_mode registers.
> 
> The TAMP (Tamper and backup registers) block is a system controller that
> provides access to backup registers as NVMEM storage that persists across
> reboots.
> 
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> 
> ---
> 
>  arch/arm64/boot/dts/st/stm32mp251.dtsi | 26 ++++++++++++++++++++++++++
>  1 file changed, 26 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/st/stm32mp251.dtsi b/arch/arm64/boot/dts/st/stm32mp251.dtsi
> index a8e6e0f77b83..c7839e732f31 100644
> --- a/arch/arm64/boot/dts/st/stm32mp251.dtsi
> +++ b/arch/arm64/boot/dts/st/stm32mp251.dtsi
> @@ -2084,6 +2084,32 @@ rtc: rtc@46000000 {
>  			status = "disabled";
>  		};
>  
> +		tamp: tamp@46010000 {
> +			compatible = "st,stm32-tamp", "syscon", "simple-mfd";
> +			#address-cells = <1>;
> +			#size-cells = <1>;
> +			reg = <0x46010000 0x400>;
> +			ranges;
> +
> +			nvram: nvram@46010100 {
> +				compatible = "st,stm32mp25-tamp-nvram";
> +				reg = <0x46010100 0x200>;
> +				nvmem-layout {
> +					compatible = "fixed-layout";
> +					#address-cells = <1>;
> +					#size-cells = <1>;
> +
> +					fwu_info: tamp-bkp@c0 {
> +						reg = <0xc0 0x4>;
> +					};
> +
> +					boot_mode: tamp-bkp@180 {
> +						reg = <0x180 0x4>;
> +					};
> +				};
> +			};
> +		};
> +
>  		pinctrl_z: pinctrl@46200000 {
>  			#address-cells = <1>;
>  			#size-cells = <1>;
Hi Dario

At STMicroelectronics we intend to upstream tamp-vram driver for STM32MP series.
If you don't see any objection, we prefer to manage it in our side.

Thanks
Patrice

  reply	other threads:[~2026-01-09 10:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-07 19:45 [PATCH 1/2] dt-bindings: nvmem: add STM32 TAMP NVRAM Dario Binacchi
2026-01-07 19:45 ` [PATCH 2/2] arm64: dts: st: add TAMP-NVRAM support for STM32MP25 Dario Binacchi
2026-01-09 10:40   ` Patrice CHOTARD [this message]
2026-01-11 15:20     ` [Linux-stm32] " Dario Binacchi
2026-01-08 16:13 ` [PATCH 1/2] dt-bindings: nvmem: add STM32 TAMP NVRAM Rob Herring
2026-01-15 14:54 ` Rob Herring

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=58006bf6-425a-4016-996b-4a01fdb22cea@foss.st.com \
    --to=patrice.chotard@foss.st.com \
    --cc=conor+dt@kernel.org \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-amarula@amarulasolutions.com \
    --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

all inboxes | Powered by JetHome®