From: Martin Kaiser <martin@kaiser.cx>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Alexander Stein <alexander.stein@ew.tq-group.com>,
linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Martin Kaiser <martin@kaiser.cx>
Subject: [PATCH v2 3/6] hwrng: imx-rngc - use polling to detect end of self test
Date: Thu, 24 Aug 2023 21:20:56 +0200 [thread overview]
Message-ID: <20230824192059.1569591-4-martin@kaiser.cx> (raw)
In-Reply-To: <20230824192059.1569591-1-martin@kaiser.cx>
Use polling to detect the end of the rngc self test. This is much simpler
than using an interrupt and a completion.
The selftest should take approx. 450us. Keep the overhead to a minimum
by polling every 500us. (We've already lowered the timeout to 1.5ms.)
Signed-off-by: Martin Kaiser <martin@kaiser.cx>
---
v2:
- use shorter timeout and polling interval
drivers/char/hw_random/imx-rngc.c | 16 +++++++---------
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git a/drivers/char/hw_random/imx-rngc.c b/drivers/char/hw_random/imx-rngc.c
index 8ff3d46674fd..09523936d2af 100644
--- a/drivers/char/hw_random/imx-rngc.c
+++ b/drivers/char/hw_random/imx-rngc.c
@@ -17,6 +17,7 @@
#include <linux/hw_random.h>
#include <linux/completion.h>
#include <linux/io.h>
+#include <linux/iopoll.h>
#include <linux/bitfield.h>
#define RNGC_VER_ID 0x0000
@@ -101,22 +102,19 @@ static inline void imx_rngc_irq_unmask(struct imx_rngc *rngc)
static int imx_rngc_self_test(struct imx_rngc *rngc)
{
- u32 cmd;
+ u32 cmd, status;
int ret;
- imx_rngc_irq_unmask(rngc);
-
/* run self test */
cmd = readl(rngc->base + RNGC_COMMAND);
writel(cmd | RNGC_CMD_SELF_TEST, rngc->base + RNGC_COMMAND);
- ret = wait_for_completion_timeout(&rngc->rng_op_done,
- usecs_to_jiffies(RNGC_SELFTEST_TIMEOUT));
- imx_rngc_irq_mask_clear(rngc);
- if (!ret)
- return -ETIMEDOUT;
+ ret = readl_poll_timeout(rngc->base + RNGC_STATUS, status,
+ status & RNGC_STATUS_ST_DONE, 500, RNGC_SELFTEST_TIMEOUT);
+ if (ret < 0)
+ return ret;
- return rngc->err_reg ? -EIO : 0;
+ return readl(rngc->base + RNGC_ERROR) ? -EIO : 0;
}
static int imx_rngc_read(struct hwrng *rng, void *data, size_t max, bool wait)
--
2.39.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-24 19:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 19:20 [PATCH v2 0/6] hwrng: imx-rngc - use polling instead of interrupt Martin Kaiser
2023-08-24 19:20 ` [PATCH v2 1/6] hwrng: imx-rngc - reasonable timeout for selftest Martin Kaiser
2023-08-24 19:20 ` [PATCH v2 2/6] hwrng: imx-rngc - reasonable timeout for initial seed Martin Kaiser
2023-08-24 19:20 ` Martin Kaiser [this message]
2023-08-25 7:12 ` [PATCH v2 3/6] hwrng: imx-rngc - use polling to detect end of self test Alexander Stein
2023-08-29 18:58 ` Martin Kaiser
2023-08-24 19:20 ` [PATCH v2 4/6] hwrng: imx-rngc - read status register for error checks Martin Kaiser
2023-08-24 19:20 ` [PATCH v2 5/6] hwrng: imx-rngc - use polling for initial seed Martin Kaiser
2023-08-24 19:20 ` [PATCH v2 6/6] hwrng: imx-rngc - remove interrupt handler Martin Kaiser
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=20230824192059.1569591-4-martin@kaiser.cx \
--to=martin@kaiser.cx \
--cc=alexander.stein@ew.tq-group.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.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).