public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: jamie@jamieiles.com (Jamie Iles)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2] hwrng: add support for picoxcell TRNG
Date: Fri, 14 Jan 2011 21:48:24 +0000	[thread overview]
Message-ID: <20110114214824.GO2822@pulham.picochip.com> (raw)
In-Reply-To: <v7p608-mqv.ln1@chipmunk.wormnet.eu>

On Fri, Jan 14, 2011 at 08:45:19PM +0000, Alexander Clouter wrote:
> In gmane.linux.ports.arm.kernel Jamie Iles <jamie@jamieiles.com> wrote:
> >
> > This driver adds support for the True Random Number Generator in
> > the Picochip PC3X3 and later devices.
> > 
> > [snipped]
> >
> > +/*
> > + * Take the random number generator out of reset and make sure the interrupts
> > + * are masked. We shouldn't need to get large amounts of random bytes so just
> > + * poll the status register. The hardware generates 32 bits every 320ns so we
> > + * shouldn't have to wait long enough to warrant waiting for an IRQ.
> > + */
> >
> timeriomem-rng?  Example of usage in 
> arch/arm/mach-orion5x/ts78xx-setup.c.

No, that's not quite suitable for our hardware.  Although the hardware 
generates the data every 320ns, it also performs self test of the data 
in hardware to make sure it satisfies certain random qualities.  If the 
data doesn't pass the tests then it's rejected and not placed into the 
FIFO so we'd have the possibility of an underflow with the 
timeriomem-rng driver.

Jamie

  reply	other threads:[~2011-01-14 21:48 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
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 [this message]
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=20110114214824.GO2822@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