From: Oleksij Rempel <o.rempel@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Oleksij Rempel <o.rempel@pengutronix.de>
Subject: [PATCH v1 1/7] nvmem: Add 'protect' operation to core framework
Date: Fri, 30 May 2025 13:41:00 +0200 [thread overview]
Message-ID: <20250530114106.1009454-2-o.rempel@pengutronix.de> (raw)
In-Reply-To: <20250530114106.1009454-1-o.rempel@pengutronix.de>
Introduce a generic "protect" operation to the NVMEM framework.
This allows NVMEM providers to expose hardware-specific protection or
locking mechanisms through the character device interface. Existing
read/write operations do not cover this type of state-altering
protection.
Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
---
drivers/nvmem/core.c | 48 ++++++++++++++++++++++++++++++++++
drivers/nvmem/partition.c | 7 +++++
include/linux/nvmem-provider.h | 5 ++++
3 files changed, 60 insertions(+)
diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
index 38dfb2cf2d1f..ac54a56f3c9f 100644
--- a/drivers/nvmem/core.c
+++ b/drivers/nvmem/core.c
@@ -30,6 +30,8 @@ struct nvmem_device {
const void *val, size_t val_size);
int (*reg_read)(void *ctx, unsigned int reg,
void *val, size_t val_size);
+ int (*reg_protect)(void *ctx, unsigned int reg,
+ size_t bytes, int prot);
};
struct nvmem_cell {
@@ -93,9 +95,54 @@ static ssize_t nvmem_cdev_write(struct cdev *cdev, const void *buf, size_t count
return retlen;
}
+static int nvmem_cdev_protect(struct cdev *cdev, size_t count, loff_t offset,
+ int prot)
+{
+ struct nvmem_device *nvmem;
+ int nvmem_prot;
+
+ if (cdev->master)
+ nvmem = container_of(cdev->master, struct nvmem_device, cdev);
+ else
+ nvmem = container_of(cdev, struct nvmem_device, cdev);
+
+ dev_dbg(cdev->dev, "protect ofs: 0x%08llx count: 0x%08zx prot: %d\n",
+ offset, count, prot);
+
+ if (!nvmem->reg_protect) {
+ dev_warn(cdev->dev, "NVMEM device %s does not support protect operation\n",
+ nvmem->name);
+ return -EOPNOTSUPP;
+ }
+
+ if (!count)
+ return 0;
+
+ if (offset >= nvmem->size || count > nvmem->size - offset) {
+ dev_err(cdev->dev, "protect range out of bounds (ofs: 0x%08llx, count 0x%08zx, size 0x%08zx)\n",
+ offset, count, nvmem->size);
+ return -EINVAL;
+ }
+
+ switch (prot) {
+ case 0:
+ nvmem_prot = NVMEM_PROTECT_ENABLE_WRITE;
+ break;
+ case 1:
+ nvmem_prot = NVMEM_PROTECT_DISABLE_WRITE;
+ break;
+ default:
+ dev_err(cdev->dev, "unsuported protection type %d\n", prot);
+ return -EINVAL;
+ }
+
+ return nvmem->reg_protect(nvmem->priv, offset, count, nvmem_prot);
+}
+
static struct cdev_operations nvmem_chrdev_ops = {
.read = nvmem_cdev_read,
.write = nvmem_cdev_write,
+ .protect = nvmem_cdev_protect,
};
static int nvmem_register_cdev(struct nvmem_device *nvmem, const char *name)
@@ -213,6 +260,7 @@ struct nvmem_device *nvmem_register(const struct nvmem_config *config)
nvmem->dev.parent = config->dev;
nvmem->reg_read = config->reg_read;
nvmem->reg_write = config->reg_write;
+ nvmem->reg_protect = config->reg_protect;
np = config->cdev ? cdev_of_node(config->cdev) : config->dev->of_node;
nvmem->dev.of_node = np;
nvmem->priv = config->priv;
diff --git a/drivers/nvmem/partition.c b/drivers/nvmem/partition.c
index d1127c1401af..bb6dbad7b5f6 100644
--- a/drivers/nvmem/partition.c
+++ b/drivers/nvmem/partition.c
@@ -18,6 +18,12 @@ static int nvmem_cdev_read(void *ctx, unsigned offset, void *buf, size_t bytes)
return cdev_read(ctx, buf, bytes, offset, 0);
}
+static int nvmem_cdev_protect(void *ctx, unsigned int offset, size_t bytes,
+ int prot)
+{
+ return cdev_protect(ctx, bytes, offset, prot);
+}
+
static int nvmem_cells_probe(struct device *dev)
{
struct nvmem_config config = {};
@@ -37,6 +43,7 @@ static int nvmem_cells_probe(struct device *dev)
config.size = cdev->size;
config.reg_read = nvmem_cdev_read;
config.reg_write = nvmem_cdev_write;
+ config.reg_protect = nvmem_cdev_protect;
return PTR_ERR_OR_ZERO(nvmem_register(&config));
}
diff --git a/include/linux/nvmem-provider.h b/include/linux/nvmem-provider.h
index c1765673eb23..991f4f9d2fa0 100644
--- a/include/linux/nvmem-provider.h
+++ b/include/linux/nvmem-provider.h
@@ -17,6 +17,9 @@
struct nvmem_device;
+#define NVMEM_PROTECT_ENABLE_WRITE 0
+#define NVMEM_PROTECT_DISABLE_WRITE 1
+
/* used for vendor specific post processing of cell data */
typedef int (*nvmem_cell_post_process_t)(void *priv, const char *id,
unsigned int offset, void *buf,
@@ -34,6 +37,8 @@ struct nvmem_config {
const void *val, size_t val_size);
int (*reg_read)(void *ctx, unsigned int reg,
void *val, size_t val_size);
+ int (*reg_protect)(void *ctx, unsigned int offset,
+ size_t bytes, int prot);
void *priv;
nvmem_cell_post_process_t cell_post_process;
};
--
2.39.5
next prev parent 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 [PATCH v1 0/7] NVMEM: Introduce write protection support Oleksij Rempel
2025-05-30 11:41 ` Oleksij Rempel [this message]
2025-06-02 9:04 ` [PATCH v1 1/7] nvmem: Add 'protect' operation to core framework 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-2-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