From: Oleksij Rempel <o.rempel@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Oleksij Rempel <o.rempel@pengutronix.de>
Subject: [PATCH v1 0/7] NVMEM: Introduce write protection support
Date: Fri, 30 May 2025 13:40:59 +0200 [thread overview]
Message-ID: <20250530114106.1009454-1-o.rempel@pengutronix.de> (raw)
This series adds a generic protect op to NVMEM core, enabling
standardized write protection. This makes NVMEM behave more like other
flash interfaces (e.g., CFI block protection), which helps with common
tooling.
Oleksij Rempel (7):
nvmem: Add 'protect' operation to core framework
nvmem: rmem: add write and protect support
commands: nvmem: Add support for creating dynamic rmem devices
regmap: Add reg_seal operation for hardware protection
nvmem: regmap: Implement protect operation using regmap_seal
nvmem: bsec: Implement NVMEM protect via regmap_seal for OTP locking
nvmem: rmem: Use unique device name for NVMEM registration
commands/nvmem.c | 124 +++++++++-
drivers/base/regmap/internal.h | 2 +
drivers/base/regmap/regmap.c | 31 +++
drivers/nvmem/bsec.c | 27 ++
drivers/nvmem/core.c | 48 ++++
drivers/nvmem/partition.c | 7 +
drivers/nvmem/regmap.c | 65 +++++
drivers/nvmem/rmem.c | 438 ++++++++++++++++++++++++++++++++-
include/linux/nvmem-provider.h | 5 +
include/linux/regmap.h | 33 +++
include/mach/stm32mp/bsec.h | 1 +
11 files changed, 774 insertions(+), 7 deletions(-)
--
2.39.5
next reply other threads:[~2025-05-30 11:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-30 11:40 Oleksij Rempel [this message]
2025-05-30 11:41 ` [PATCH v1 1/7] nvmem: Add 'protect' operation to core framework Oleksij Rempel
2025-06-02 9:04 ` Sascha Hauer
2025-05-30 11:41 ` [PATCH v1 2/7] nvmem: rmem: add write and protect support Oleksij Rempel
2025-06-02 9:33 ` Sascha Hauer
2025-05-30 11:41 ` [PATCH v1 3/7] commands: nvmem: Add support for creating dynamic rmem devices Oleksij Rempel
2025-06-02 9:41 ` Sascha Hauer
2025-05-30 11:41 ` [PATCH v1 4/7] regmap: Add reg_seal operation for hardware protection Oleksij Rempel
2025-06-02 9:47 ` Sascha Hauer
2025-05-30 11:41 ` [PATCH v1 5/7] nvmem: regmap: Implement protect operation using regmap_seal Oleksij Rempel
2025-06-02 9:57 ` Sascha Hauer
2025-05-30 11:41 ` [PATCH v1 6/7] nvmem: bsec: Implement NVMEM protect via regmap_seal for OTP locking Oleksij Rempel
2025-05-30 11:41 ` [PATCH v1 7/7] nvmem: rmem: Use unique device name for NVMEM registration Oleksij Rempel
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=20250530114106.1009454-1-o.rempel@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=barebox@lists.infradead.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