From: Sascha Hauer <s.hauer@pengutronix.de>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2 3/5] nvmem: expose nvmem cells as cdev
Date: Fri, 14 Jun 2024 09:46:58 +0200 [thread overview]
Message-ID: <Zmv1cicAOuRI4PGO@pengutronix.de> (raw)
In-Reply-To: <20240613131531.364894-3-m.felsch@pengutronix.de>
On Thu, Jun 13, 2024 at 03:15:29PM +0200, Marco Felsch wrote:
> Expose the nvmem cells via cdevs which is our equivalent to the Linux
> sysfs exposure. This allows the easier user queries for board code and
> shell. Keep the Linux function name scheme for
> nvmem_populate_sysfs_cells() to reduce the diff for nvmem_register()
> function.
>
> Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
> ---
> v2:
> - fix error handling path during nvmem_register
> - drop useless list_empty()
>
> drivers/nvmem/core.c | 101 +++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 101 insertions(+)
>
> diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
> index ee7d4c6301c3..8e91d9c0fc8a 100644
> --- a/drivers/nvmem/core.c
> +++ b/drivers/nvmem/core.c
> @@ -44,6 +44,8 @@ struct nvmem_cell_entry {
> struct device_node *np;
> struct nvmem_device *nvmem;
> struct list_head node;
> +
> + struct cdev cdev;
> };
>
> struct nvmem_cell {
> @@ -144,6 +146,101 @@ static struct nvmem_device *of_nvmem_find(struct device_node *nvmem_np)
> return NULL;
> }
>
> +static struct nvmem_cell *nvmem_create_cell(struct nvmem_cell_entry *entry,
> + const char *id, int index);
> +
> +static ssize_t nvmem_cell_cdev_read(struct cdev *cdev, void *buf, size_t count,
> + loff_t offset, unsigned long flags)
> +{
> + struct nvmem_cell_entry *entry;
> + struct nvmem_cell *cell = NULL;
> + size_t cell_sz, read_len;
> + void *content;
> +
> + entry = container_of(cdev, struct nvmem_cell_entry, cdev);
> + cell = nvmem_create_cell(entry, entry->name, 0);
> + if (IS_ERR(cell))
> + return PTR_ERR(cell);
> +
> + content = nvmem_cell_read(cell, &cell_sz);
> + if (IS_ERR(content)) {
> + read_len = PTR_ERR(content);
> + goto destroy_cell;
> + }
> +
> + read_len = min_t(unsigned int, cell_sz - offset, count);
> + memcpy(buf, content + offset, read_len);
> + kfree(content);
> +
> +destroy_cell:
> + kfree_const(cell->id);
> + kfree(cell);
> +
> + return read_len;
> +}
> +
> +static ssize_t nvmem_cell_cdev_write(struct cdev *cdev, const void *buf, size_t count,
> + loff_t offset, unsigned long flags)
> +{
> + struct nvmem_cell_entry *entry;
> + struct nvmem_cell *cell;
> + int ret;
> +
> + entry = container_of(cdev, struct nvmem_cell_entry, cdev);
> +
> + if (!entry->nvmem->reg_write)
> + return -EPERM;
> +
> + if (offset >= entry->bytes)
> + return -EFBIG;
> +
> + if (offset + count > entry->bytes)
> + count = entry->bytes - offset;
> +
> + cell = nvmem_create_cell(entry, entry->name, 0);
> + if (IS_ERR(cell))
> + return PTR_ERR(cell);
> +
> + if (!cell)
> + return -EINVAL;
> +
> + ret = nvmem_cell_write(cell, buf, count);
> +
> + kfree_const(cell->id);
> + kfree(cell);
> +
> + return ret;
> +}
> +
> +static struct cdev_operations nvmem_cell_chrdev_ops = {
> + .read = nvmem_cell_cdev_read,
> + .write = nvmem_cell_cdev_write,
> +};
> +
> +static int nvmem_populate_sysfs_cells(struct nvmem_device *nvmem)
> +{
> + struct device *dev = &nvmem->dev;
> + struct nvmem_cell_entry *entry;
> +
> + list_for_each_entry(entry, &nvmem->cells, node) {
> + struct cdev *cdev;
> + int ret;
> +
> + cdev = &entry->cdev;
> + cdev->name = xasprintf("%s.%s", dev_name(dev),
> + kbasename(entry->name));
> + cdev->ops = &nvmem_cell_chrdev_ops;
> + cdev->dev = dev;
> + cdev->size = entry->bytes;
> +
> + ret = devfs_create(cdev);
> + if (ret)
> + return ret;
You might fail here without unregistering the already registered cells.
Furthermore you free the nvmem device which likely leads to memory
corruptions further down. Your choices are:
- Do not fail here, but only print a warning when devfs_create() fails,
or:
- properly unregister what you registered beforehand.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2024-06-14 7:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 13:15 [PATCH v2 1/5] nvmem: fix nvmem_register error path Marco Felsch
2024-06-13 13:15 ` [PATCH v2 2/5] nvmem: sync with linux code base Marco Felsch
2024-06-13 13:15 ` [PATCH v2 3/5] nvmem: expose nvmem cells as cdev Marco Felsch
2024-06-14 7:46 ` Sascha Hauer [this message]
2024-06-14 10:31 ` Marco Felsch
2024-06-13 13:15 ` [PATCH v2 4/5] nvmem: allow single and dynamic device ids Marco Felsch
2024-06-13 13:15 ` [PATCH v2 5/5] eeprom: at24: fix device name handling Marco Felsch
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=Zmv1cicAOuRI4PGO@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=m.felsch@pengutronix.de \
/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