linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
To: gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, srinivas.kandagatla@linaro.org
Subject: [RESEND PATCH 05/20] nvmem: sunxi_sid: Optimize register read-out method
Date: Sat, 13 Apr 2019 11:32:50 +0100	[thread overview]
Message-ID: <20190413103305.9576-6-srinivas.kandagatla@linaro.org> (raw)
In-Reply-To: <20190413103305.9576-1-srinivas.kandagatla@linaro.org>

From: Chen-Yu Tsai <wens@csie.org>

SID cells are 32-bit aligned, and a multiple of 32 bits in length. The
only outlier is the thermal sensor calibration data, which is 16 bits
per sensor. However a whole 64 bits is allocated for this purpose, so
we could consider it conforming to the rule above.

Also, the register read-out method assumes native endian, unlike the
direct MMIO method, which assumes big endian. Thus no endian conversion
is involved.

Under these assumptions, the register read-out method can be slightly
optimized. Instead of reading one word then discarding 3 bytes, read
the whole word directly into the buffer. However, for reads under 4
bytes or trailing bytes, we still use a scratch buffer to extract the
requested bytes.

We could go one step further if .word_size was 4, but changing that
would affect the sysfs interface's behavior.

Signed-off-by: Chen-Yu Tsai <wens@csie.org>
Acked-by: Maxime Ripard <maxime.ripard@bootlin.com>
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
---
 drivers/nvmem/sunxi_sid.c | 38 ++++++++++++++++++--------------------
 1 file changed, 18 insertions(+), 20 deletions(-)

diff --git a/drivers/nvmem/sunxi_sid.c b/drivers/nvmem/sunxi_sid.c
index 704c35edf796..15fbfab62595 100644
--- a/drivers/nvmem/sunxi_sid.c
+++ b/drivers/nvmem/sunxi_sid.c
@@ -115,36 +115,34 @@ static int sun8i_sid_register_readout(const struct sunxi_sid *sid,
  * to be not reliable at all.
  * Read by the registers instead.
  */
-static int sun8i_sid_read_byte_by_reg(const struct sunxi_sid *sid,
-				      const unsigned int offset,
-				      u8 *out)
-{
-	u32 word;
-	int ret;
-
-	ret = sun8i_sid_register_readout(sid, offset & ~0x03, &word);
-
-	if (ret)
-		return ret;
-
-	*out = (word >> ((offset & 0x3) * 8)) & 0xff;
-
-	return 0;
-}
-
 static int sun8i_sid_read_by_reg(void *context, unsigned int offset,
 				 void *val, size_t bytes)
 {
 	struct sunxi_sid *sid = context;
-	u8 *buf = val;
+	u32 word;
 	int ret;
 
-	while (bytes--) {
-		ret = sun8i_sid_read_byte_by_reg(sid, offset++, buf++);
+	/* .stride = 4 so offset is guaranteed to be aligned */
+	while (bytes >= 4) {
+		ret = sun8i_sid_register_readout(sid, offset, val);
 		if (ret)
 			return ret;
+
+		val += 4;
+		offset += 4;
+		bytes -= 4;
 	}
 
+	if (!bytes)
+		return 0;
+
+	/* Handle any trailing bytes */
+	ret = sun8i_sid_register_readout(sid, offset, &word);
+	if (ret)
+		return ret;
+
+	memcpy(val, &word, bytes);
+
 	return 0;
 }
 
-- 
2.21.0


  parent reply	other threads:[~2019-04-13 10:33 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 ` Srinivas Kandagatla [this message]
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 ` [RESEND PATCH 12/20] nvmem: core: add nvmem_cell_read_u16 Srinivas Kandagatla
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-6-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).