From: David Daney <ddaney@caviumnetworks.com>
To: Ralf Baechle <ralf@linux-mips.org>,
akpm@linux-foundation.org,
Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-mips <linux-mips@linux-mips.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] New hardware RNG for Octeon SOCs.
Date: Mon, 10 Aug 2009 11:21:29 -0700 [thread overview]
Message-ID: <4A806529.3060609@caviumnetworks.com> (raw)
Behold the Random Number Generator driver for Octeon!
The first patch adds some port definitions and the octeon_rng platform
device. The second is the driver.
I am copying AKPM and Linus as there seems to be no hw_random maintainer.
Since Octeon is a mips port, we might want to merge both patches via
Ralf's tree.
Comments?
David Daney (2):
MIPS: Octeon: Add hardware RNG platform device.
hw_random: Add hardware RNG for Octeon SOCs.
arch/mips/cavium-octeon/setup.c | 44 ++++++++
arch/mips/include/asm/octeon/cvmx-rnm-defs.h | 86 +++++++++++++++
drivers/char/hw_random/Kconfig | 13 +++
drivers/char/hw_random/Makefile | 1 +
drivers/char/hw_random/octeon-rng.c | 146
++++++++++++++++++++++++++
5 files changed, 290 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-10 18:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 18:21 David Daney [this message]
2009-08-10 18:30 ` [PATCH 1/2] MIPS: Octeon: Add hardware RNG platform device David Daney
2009-08-10 22:35 ` Andrew Morton
2009-08-10 22:35 ` Andrew Morton
2009-08-10 18:30 ` [PATCH 2/2] hw_random: Add hardware RNG for Octeon SOCs David Daney
2009-08-10 22:35 ` Andrew Morton
2009-08-10 22:35 ` Andrew Morton
2009-08-10 19:54 ` [PATCH 0/2] New " Matt Mackall
2009-08-10 19:57 ` David Daney
2009-08-10 20:18 ` [PATCH] MAINTAINERS: Add Matt Mackall and Herbert Xu to HARDWARE RANDOM NUMBER GENERATOR Joe Perches
2009-08-10 22:34 ` [PATCH 0/2] New hardware RNG for Octeon SOCs Andrew Morton
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=4A806529.3060609@caviumnetworks.com \
--to=ddaney@caviumnetworks.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=torvalds@linux-foundation.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).