public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: linux-kernel@vger.kernel.org, linux-amarula@amarulasolutions.com,
	Alexandre Torgue <alexandre.torgue@foss.st.com>,
	Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Srinivas Kandagatla <srini@kernel.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH 1/2] dt-bindings: nvmem: add STM32 TAMP NVRAM
Date: Thu, 15 Jan 2026 08:54:12 -0600	[thread overview]
Message-ID: <20260115145412.GA621905-robh@kernel.org> (raw)
In-Reply-To: <20260107194541.1843999-1-dario.binacchi@amarulasolutions.com>

On Wed, Jan 07, 2026 at 08:45:32PM +0100, Dario Binacchi wrote:
> Add devicetree bindings for TAMP backup registers. These 32-bit
> registers are retained in all low-power modes and in VBAT mode. As a
> result, they can also be used to store sensitive data because their
> content is protected by a tamper detection circuit.
> 
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> ---
> 
>  .../bindings/nvmem/st,stm32-tamp-nvram.yaml   | 55 +++++++++++++++++++
>  1 file changed, 55 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/nvmem/st,stm32-tamp-nvram.yaml
> 
> diff --git a/Documentation/devicetree/bindings/nvmem/st,stm32-tamp-nvram.yaml b/Documentation/devicetree/bindings/nvmem/st,stm32-tamp-nvram.yaml
> new file mode 100644
> index 000000000000..e03469fbe436
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/nvmem/st,stm32-tamp-nvram.yaml
> @@ -0,0 +1,55 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/nvmem/st,stm32-tamp-nvram.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: STMicroelectronics STM32 TAMP's NVRAM
> +
> +description: |

Don't need '|' if no formatting.

> +  The TAMP peripheral integrates, amongst others, Non Volatile RAM

What others? Are you saying this binding is incomplete?

> +  (NVRAM) with 32/128 32-bit backup registers which can be used by
> +  software to store information or communicate with a boot loader.

Wrap lines at 80 char.

> +
> +maintainers:
> +  - Dario Binacchi <dario.binacchi@amarulasolutions.com>
> +
> +allOf:
> +  - $ref: nvmem.yaml#
> +
> +properties:
> +  compatible:
> +    enum:
> +      - st,stm32mp15-tamp-nvram
> +      - st,stm32mp25-tamp-nvram
> +
> +  reg:
> +    maxItems: 1
> +
> +required:
> +  - compatible
> +  - reg
> +
> +unevaluatedProperties: false
> +
> +examples:
> +  - |
> +    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>;
> +            };
> +        };
> +    };
> +...
> -- 
> 2.43.0
> 
> base-commit: f0b9d8eb98dfee8d00419aa07543bdc2c1a44fb1
> branch: stm32-tamp-nvram

      parent reply	other threads:[~2026-01-15 14:54 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   ` [Linux-stm32] " Patrice CHOTARD
2026-01-11 15:20     ` 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 [this message]

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=20260115145412.GA621905-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=alexandre.torgue@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=srini@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