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>,
Christophe Roullier <christophe.roullier@foss.st.com>,
Srinivas Kandagatla <srini@kernel.org>
Cc: Simeon Marijon <simeon.marijon@foss.st.com>,
<linux-stm32@st-md-mailman.stormreply.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Gatien Chevallier <gatien.chevallier@foss.st.com>
Subject: Re: [PATCH v4 0/3] Add STM32 TAMP nvram driver support
Date: Thu, 5 Nov 2026 12:39:58 +0100 [thread overview]
Message-ID: <14c013e7-da82-4f5b-8eb8-f95abb1b9e34@foss.st.com> (raw)
In-Reply-To: <20261104-upstream_nvram_reworked-v4-0-144024496a44@foss.st.com>
Don't take care of this series, a new one is on-going which will include https://patchwork.kernel.org/series/1176665/
On 11/4/26 16:20, Patrice Chotard wrote:
> Propose bindings and driver to enable TAMP nvram driver
> support for STM32MP SoC's family.
> It allows to expose TAMP backup registers as nvmem cells.
>
> Signed-off-by: Patrice Chotard <patrice.chotard@foss.st.com>
> ---
> Changes in v4:
> - Make usage of of_device_get_match_data() wrapper.
> - Rework ioremap of syscon's memory region to avoid overlapping
> between parent and child node. This allows to remove
> bkpregs_regmap_cfg declaration for both STM32MP1 and STM32MP2.
> _ Add select MFD_SYSCON in Kconfig.
> - Link to v3: https://patch.msgid.link/20261016-upstream_nvram_reworked-v3-0-f65908490cf7@foss.st.com
>
> Changes in v3:
> - Fix issue found by sashiko-bot:
> - rely on the already resolved priv->data->nb_zones instead of
> of_device_is_compatible() to set priv->bkpreg_access
> - Fix max_register of stm32mp1_tamp_nvram_regmap_cfg and
> stm32mp2_tamp_nvram_regmap_cfg
> - Update zones_end type to int*
> - Replace both memcpy by put_unaligned_le32 and get_unaligned_le32
> - Link to v2: https://patch.msgid.link/20260930-upstream_nvram_reworked-v2-0-cfda749ee0b7@foss.st.com
>
> Changes in v2:
> - Update commit title of nvmem dt-bindings's patch.
> - Add required compatible for patternProperties in stm32/st,stm32-syscon.yaml.
> - Fix issue found by sashiko-bot:
> - Add freeing compartment_owner.
> - Replace regmap_read/regmap_write by regmap_update_bits in stm32_tamp_nvram_write_byte().
> - Update error return in stm32_tamp_nvram_read_byte(), stm32_tamp_nvram_write_byte(),
> stm32_tamp_nvram_read() and stm32_tamp_nvram_write() to return the actual regmap_read() /
> regmap_write() error instead of -EIO.
> - Add freeing field and update error return values for stm32_tamp_nvram_get_backup_zones().
> - Update error return for stm32_tamp_nvram_probe().
> - Link to v1: https://patch.msgid.link/20260910-upstream_nvram_reworked-v1-0-521c16175cef@foss.st.com
>
> To: Simeon Marijon <simeon.marijon@foss.st.com>
> To: Patrice Chotard <patrice.chotard@foss.st.com>
> To: Srinivas Kandagatla <srini@kernel.org>
> To: Rob Herring <robh@kernel.org>
> To: Krzysztof Kozlowski <krzk+dt@kernel.org>
> To: Conor Dooley <conor+dt@kernel.org>
> To: Maxime Coquelin <mcoquelin.stm32@gmail.com>
> To: Alexandre Torgue <alexandre.torgue@foss.st.com>
> To: Christophe Roullier <christophe.roullier@foss.st.com>
> Cc: linux-stm32@st-md-mailman.stormreply.com
> Cc: devicetree@vger.kernel.org
> Cc: linux-arm-kernel@lists.infradead.org
> Cc: linux-kernel@vger.kernel.org
>
> ---
> Patrice Chotard (1):
> dt-bindings: arm: stm32: allow TAMP nvram child node for syscon
>
> Simeon Marijon (2):
> dt-bindings: nvmem: add STM32MPX TAMP backup registers
> nvmem: stm32: add TAMP nvmem driver
>
> .../bindings/arm/stm32/st,stm32-syscon.yaml | 38 +-
> .../bindings/nvmem/st,stm32-tamp-nvram.yaml | 57 ++
> MAINTAINERS | 8 +
> drivers/nvmem/Kconfig | 11 +
> drivers/nvmem/Makefile | 2 +
> drivers/nvmem/stm32-tamp-nvram.c | 680 +++++++++++++++++++++
> 6 files changed, 793 insertions(+), 3 deletions(-)
> ---
> base-commit: 6628e7d4c6b25c8d18f1345e3a20d21829aae7e4
> change-id: 20260909-upstream_nvram_reworked-f84a4b37817c
>
> Best regards,
> --
> Patrice Chotard <patrice.chotard@foss.st.com>
>
prev parent reply other threads:[~2026-11-05 11:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 15:20 Patrice Chotard
2026-11-04 15:20 ` [PATCH v4 1/3] dt-bindings: nvmem: add STM32MPX TAMP backup registers Patrice Chotard
2026-11-06 10:16 ` Krzysztof Kozlowski
2026-11-06 10:33 ` Patrice CHOTARD
2026-11-06 11:00 ` Krzysztof Kozlowski
2026-11-06 11:13 ` Patrice CHOTARD
2026-11-04 15:20 ` [PATCH v4 2/3] dt-bindings: arm: stm32: allow TAMP nvram child node for syscon Patrice Chotard
2026-11-06 10:21 ` Krzysztof Kozlowski
2026-11-06 10:46 ` Patrice CHOTARD
2026-11-04 15:20 ` [PATCH v4 3/3] nvmem: stm32: add TAMP nvmem driver Patrice Chotard
2026-11-05 11:39 ` Patrice CHOTARD [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=14c013e7-da82-4f5b-8eb8-f95abb1b9e34@foss.st.com \
--to=patrice.chotard@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=christophe.roullier@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gatien.chevallier@foss.st.com \
--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 \
--cc=simeon.marijon@foss.st.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
all inboxes | Powered by JetHome®