From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] hwrng: add support for picoxcell TRNG
Date: Fri, 14 Jan 2011 18:16:09 +0000 [thread overview]
Message-ID: <20110114181609.GN2822@pulham.picochip.com> (raw)
In-Reply-To: <1295027353.30392.20.camel@calx>
Hi Matt,
Many thanks for the quick feedback!
On Fri, Jan 14, 2011 at 11:49:13AM -0600, Matt Mackall wrote:
> On Fri, 2011-01-14 at 16:10 +0000, Jamie Iles wrote:
> > This driver adds support for the True Random Number Generator in
> > diff --git a/drivers/char/hw_random/Makefile
> > b/drivers/char/hw_random/Makefile
> > index 4273308..3db4eb8 100644
> > --- a/drivers/char/hw_random/Makefile
> > +++ b/drivers/char/hw_random/Makefile
> > @@ -19,3 +19,4 @@ obj-$(CONFIG_HW_RANDOM_TX4939) += tx4939-rng.o
> > obj-$(CONFIG_HW_RANDOM_MXC_RNGA) += mxc-rnga.o
> > obj-$(CONFIG_HW_RANDOM_OCTEON) += octeon-rng.o
> > obj-$(CONFIG_HW_RANDOM_NOMADIK) += nomadik-rng.o
> > +obj-$(CONFIG_HW_RANDOM_PICOXCELL) += picoxcell-rng.o
> > diff --git a/drivers/char/hw_random/picoxcell-rng.c b/drivers/char/hw_random/picoxcell-rng.c
> > new file mode 100644
> > index 0000000..e750056
> > --- /dev/null
> > +++ b/drivers/char/hw_random/picoxcell-rng.c
> > @@ -0,0 +1,175 @@
> > +/*
> > + * Copyright (c) 2010-2011 Picochip Ltd., Jamie Iles
> > + *
> > + * This program is free software; you can redistribute it and/or modify
> > + * it under the terms of the GNU General Public License version 2 as
> > + * published by the Free Software Foundation.
> > + *
> > + * All enquiries to support at picochip.com
> > + */
> > +#include <linux/clk.h>
> > +#include <linux/err.h>
> > +#include <linux/hw_random.h>
> > +#include <linux/io.h>
> > +#include <linux/kernel.h>
> > +#include <linux/module.h>
> > +#include <linux/platform_device.h>
> > +
> > +#define DATA_REG_OFFSET 0x0200
> > +#define CSR_REG_OFFSET 0x0278
> > +#define CSR_OUT_EMPTY_MASK (1 << 24)
> > +#define TAI_REG_OFFSET 0x0380
>
> Some whitespace weirdness here. Recommend never using tabs except at the
> beginning of a line.
I'll fix that up, not sure what happened there.
> > +static void __iomem *rng_base;
> > +static struct clk *rng_clk;
> > +
> > +/*
> > + * Get some random data from the random number generator. The hw_random core
> > + * layer provides us with locking. We can't rely on data being word aligned
> > + * though so we'll need to do a memcpy.
> > + */
> > +static int picoxcell_trng_read(struct hwrng *rng, void *buf, size_t max,
> > + bool wait)
> > +{
> > + u32 __iomem *csr = rng_base + CSR_REG_OFFSET;
> > + int data_avail = !(__raw_readl(csr) & CSR_OUT_EMPTY_MASK);
> > + u32 data;
> > +
> > + if (!data_avail && !wait)
> > + return 0;
> > +
> > + /* Wait for some data to become available. */
> > + while (!data_avail) {
> > + data_avail = !(__raw_readl(csr) & CSR_OUT_EMPTY_MASK);
> > + cpu_relax();
> > + }
>
> This could be simplified a bit:
>
> - deduplicate avail check
> - only relax when data's not available
> - drop some one use vars
>
> while (!__raw_read(rng_base + ...) {
> if (!wait)
> return;
> cpu_relax();
> }
Yes, that's much neater.
> > + data = __raw_readl(rng_base + DATA_REG_OFFSET);
> > + memcpy(buf, &data, min(max, sizeof(data)));
>
> The buffer passed in is guaranteed aligned:
>
> static u8 rng_buffer[SMP_CACHE_BYTES < 32 ? 32 : SMP_CACHE_BYTES]
> __cacheline_aligned;
> ...
> return rng->read(rng, (void *)buffer, size, wait);
Ok, that makes sense. I must have confused myself with the __user
buffer which doesn't have any alignment guarantees.
Thanks again for the review, I'll get a respin out early next week.
Jamie
next prev parent reply other threads:[~2011-01-14 18:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 16:10 [PATCH] hwrng: add support for picoxcell TRNG Jamie Iles
2011-01-14 17:49 ` Matt Mackall
2011-01-14 18:16 ` Jamie Iles [this message]
2011-01-14 18:44 ` [PATCHv2] " Jamie Iles
2011-01-14 18:48 ` Matt Mackall
2011-01-14 20:45 ` Alexander Clouter
2011-01-14 21:48 ` Jamie Iles
2011-01-15 0:44 ` Herbert Xu
2011-01-17 10:23 ` Jamie Iles
2011-01-23 8:00 ` Herbert Xu
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=20110114181609.GN2822@pulham.picochip.com \
--to=jamie@jamieiles.com \
--cc=linux-arm-kernel@lists.infradead.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