From: David Daney <ddaney@caviumnetworks.com>
To: ralf@linux-mips.org, mpm@selenic.com, herbert@gondor.apana.org.au
Cc: linux-mips@linux-mips.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] New hardware RNG for Octeon SOCs (v2)
Date: Thu, 20 Aug 2009 14:07:35 -0700 [thread overview]
Message-ID: <4A8DBB17.5020301@caviumnetworks.com> (raw)
Based on feedback from AKPM, I have a new revision of the Octeon
hardware RNG driver.
The changes from v1 are minor, just eliminating some bogus casting by
accessing the driver state by embedding struct hwrng in the driver
data, which is now accessed with the container_of() trick.
The first patch adds some port definitions and the octeon_rng platform
device. The second is the driver.
Since Octeon is a mips port, we might want to merge both patches via
Ralf's linux-mips.org tree.
David Daney (2):
MIPS: Octeon: Add hardware RNG platform device.
hw_random: Add hardware RNG for Octeon SOCs.
arch/mips/cavium-octeon/setup.c | 43 ++++++++
arch/mips/include/asm/octeon/cvmx-rnm-defs.h | 88 +++++++++++++++
drivers/char/hw_random/Kconfig | 13 +++
drivers/char/hw_random/Makefile | 1 +
drivers/char/hw_random/octeon-rng.c | 147
++++++++++++++++++++++++++
5 files changed, 292 insertions(+), 0 deletions(-)
create mode 100644 arch/mips/include/asm/octeon/cvmx-rnm-defs.h
create mode 100644 drivers/char/hw_random/octeon-rng.c
next reply other threads:[~2009-08-20 21:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 21:07 David Daney [this message]
2009-08-20 21:10 ` [PATCH 1/2] MIPS: Octeon: Add hardware RNG platform device David Daney
2009-08-24 7:47 ` Herbert Xu
2009-08-27 14:55 ` Ralf Baechle
2009-08-20 21:10 ` [PATCH 2/2] hw_random: Add hardware RNG for Octeon SOCs David Daney
2009-08-24 7:47 ` Herbert Xu
2009-08-27 14:56 ` Ralf Baechle
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=4A8DBB17.5020301@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=akpm@linux-foundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mpm@selenic.com \
--cc=ralf@linux-mips.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).