summaryrefslogtreecommitdiffstats
path: root/drivers/nvmem
diff options
context:
space:
mode:
authorAndrey Smirnov <andrew.smirnov@gmail.com>2019-01-28 22:55:34 -0800
committerSascha Hauer <s.hauer@pengutronix.de>2019-01-29 09:27:03 +0100
commit570acd05ff0238aedf2c3aff4873edec1123dac9 (patch)
tree8cf87caca59d0ee27a753c9c0574e99d77c3bcb6 /drivers/nvmem
parent6f37d9efd9183ff06e65438e349ac2341d459290 (diff)
downloadbarebox-570acd05ff0238aedf2c3aff4873edec1123dac9.tar.gz
barebox-570acd05ff0238aedf2c3aff4873edec1123dac9.tar.xz
nvmem: Do not use DEVFS_IS_CHARACTER_DEV
There doesn't appear any good reason to mark NVMEM cdevs as DEVFS_IS_CHARACTER_DEV, since NVMEM devices should be able to read/write data at arbitrary offsets and are not different from any other cdevs representing non-volatile storage. Signed-off-by: Andrey Smirnov <andrew.smirnov@gmail.com> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'drivers/nvmem')
-rw-r--r--drivers/nvmem/core.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
index 63c0f997b3..9fd599095c 100644
--- a/drivers/nvmem/core.c
+++ b/drivers/nvmem/core.c
@@ -96,7 +96,6 @@ static int nvmem_register_cdev(struct nvmem_device *nvmem, const char *name)
alias = of_alias_get(dev->device_node);
nvmem->cdev.name = xstrdup(alias ?: name);
- nvmem->cdev.flags = DEVFS_IS_CHARACTER_DEV;
nvmem->cdev.ops = &nvmem_chrdev_ops;
nvmem->cdev.dev = &nvmem->dev;
nvmem->cdev.size = nvmem->size;