From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, srinivas.kandagatla@linaro.org
Subject: [RESEND PATCH 12/20] nvmem: core: add nvmem_cell_read_u16
Date: Sat, 13 Apr 2019 11:32:57 +0100 [thread overview]
Message-ID: <20190413103305.9576-13-srinivas.kandagatla@linaro.org> (raw)
In-Reply-To: <20190413103305.9576-1-srinivas.kandagatla@linaro.org>
From: Fabrice Gasnier <fabrice.gasnier@st.com>
Add nvmem_cell_read_u16() helper to ease read of an u16 value on consumer
side. This is inspired by nvmem_cell_read_u32() function.
This helper is useful on stm32 that has 16 bits data cells stored in non
volatile memory.
Signed-off-by: Fabrice Gasnier <fabrice.gasnier@st.com>
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
---
drivers/nvmem/core.c | 37 ++++++++++++++++++++++++++++++++++
include/linux/nvmem-consumer.h | 7 +++++++
2 files changed, 44 insertions(+)
diff --git a/drivers/nvmem/core.c b/drivers/nvmem/core.c
index f24008b66826..1d00f5671368 100644
--- a/drivers/nvmem/core.c
+++ b/drivers/nvmem/core.c
@@ -1334,6 +1334,43 @@ int nvmem_cell_write(struct nvmem_cell *cell, void *buf, size_t len)
}
EXPORT_SYMBOL_GPL(nvmem_cell_write);
+/**
+ * nvmem_cell_read_u16() - Read a cell value as an u16
+ *
+ * @dev: Device that requests the nvmem cell.
+ * @cell_id: Name of nvmem cell to read.
+ * @val: pointer to output value.
+ *
+ * Return: 0 on success or negative errno.
+ */
+int nvmem_cell_read_u16(struct device *dev, const char *cell_id, u16 *val)
+{
+ struct nvmem_cell *cell;
+ void *buf;
+ size_t len;
+
+ cell = nvmem_cell_get(dev, cell_id);
+ if (IS_ERR(cell))
+ return PTR_ERR(cell);
+
+ buf = nvmem_cell_read(cell, &len);
+ if (IS_ERR(buf)) {
+ nvmem_cell_put(cell);
+ return PTR_ERR(buf);
+ }
+ if (len != sizeof(*val)) {
+ kfree(buf);
+ nvmem_cell_put(cell);
+ return -EINVAL;
+ }
+ memcpy(val, buf, sizeof(*val));
+ kfree(buf);
+ nvmem_cell_put(cell);
+
+ return 0;
+}
+EXPORT_SYMBOL_GPL(nvmem_cell_read_u16);
+
/**
* nvmem_cell_read_u32() - Read a cell value as an u32
*
diff --git a/include/linux/nvmem-consumer.h b/include/linux/nvmem-consumer.h
index 312bfa5efd80..8f8be5b00060 100644
--- a/include/linux/nvmem-consumer.h
+++ b/include/linux/nvmem-consumer.h
@@ -61,6 +61,7 @@ void nvmem_cell_put(struct nvmem_cell *cell);
void devm_nvmem_cell_put(struct device *dev, struct nvmem_cell *cell);
void *nvmem_cell_read(struct nvmem_cell *cell, size_t *len);
int nvmem_cell_write(struct nvmem_cell *cell, void *buf, size_t len);
+int nvmem_cell_read_u16(struct device *dev, const char *cell_id, u16 *val);
int nvmem_cell_read_u32(struct device *dev, const char *cell_id, u32 *val);
/* direct nvmem device read/write interface */
@@ -122,6 +123,12 @@ static inline int nvmem_cell_write(struct nvmem_cell *cell,
return -EOPNOTSUPP;
}
+static inline int nvmem_cell_read_u16(struct device *dev,
+ const char *cell_id, u16 *val)
+{
+ return -EOPNOTSUPP;
+}
+
static inline int nvmem_cell_read_u32(struct device *dev,
const char *cell_id, u32 *val)
{
--
2.21.0
next prev parent reply other threads:[~2019-04-13 10:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-13 10:32 [RESEND PATCH 00/20] nvmem: patches(set 1) for 5.2 Srinivas Kandagatla
2019-04-13 10:32 ` [RESEND PATCH 01/20] dt-bindings: imx-ocotp: Add i.MX8MQ compatible Srinivas Kandagatla
2019-04-13 10:32 ` [RESEND PATCH 02/20] nvmem: imx-ocotp: add support for imx8mq Srinivas Kandagatla
2019-04-13 10:32 ` [RESEND PATCH 03/20] nvmem: imx-ocotp: broaden Kconfig dependency Srinivas Kandagatla
2019-04-13 10:32 ` [RESEND PATCH 04/20] nvmem: sunxi_sid: Read out SID for randomness without looping Srinivas Kandagatla
2019-04-13 10:32 ` [RESEND PATCH 05/20] nvmem: sunxi_sid: Optimize register read-out method Srinivas Kandagatla
2019-04-13 10:32 ` [RESEND PATCH 06/20] nvmem: sunxi_sid: Dynamically allocate nvmem_config structure Srinivas Kandagatla
2019-04-13 10:32 ` [RESEND PATCH 07/20] nvmem: sunxi_sid: Read out data in native format Srinivas Kandagatla
2019-04-13 10:32 ` [RESEND PATCH 08/20] nvmem: sunxi_sid: Support SID on A83T and H5 Srinivas Kandagatla
2019-04-13 10:32 ` [RESEND PATCH 09/20] dt-bindings: nvmem: Add STM32 factory-programmed romem Srinivas Kandagatla
2019-04-13 10:32 ` [RESEND PATCH 10/20] nvmem: Add driver for STM32 factory-programmed read only mem Srinivas Kandagatla
2019-04-13 10:32 ` [RESEND PATCH 11/20] nvmem: stm32: add support for STM32MP15 BSEC to control OTP data Srinivas Kandagatla
2019-04-13 10:32 ` Srinivas Kandagatla [this message]
2019-04-13 10:32 ` [RESEND PATCH 13/20] nvmem: core: fix read buffer in place Srinivas Kandagatla
2019-04-13 10:32 ` [RESEND PATCH 14/20] nvmem: imx-ocotp: use devm_platform_ioremap_resource() to simplify code Srinivas Kandagatla
2019-04-13 10:33 ` [RESEND PATCH 15/20] nvmem: mxs-ocotp: " Srinivas Kandagatla
2019-04-13 10:33 ` [RESEND PATCH 16/20] nvmem: imx-iim: " Srinivas Kandagatla
2019-04-13 10:33 ` [RESEND PATCH 17/20] nvmem: sunxi-sid: fix wrong description in kernel doc Srinivas Kandagatla
2019-04-13 10:33 ` [RESEND PATCH 18/20] nvmem: sunxi-sid: add binding for H6's SID controller Srinivas Kandagatla
2019-04-13 10:33 ` [RESEND PATCH 19/20] nvmem: sunxi-sid: convert to SPDX license tags Srinivas Kandagatla
2019-04-13 10:33 ` [RESEND PATCH 20/20] nvmem: sunxi_sid: Support SID on H6 Srinivas Kandagatla
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=20190413103305.9576-13-srinivas.kandagatla@linaro.org \
--to=srinivas.kandagatla@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).