From: Lokesh Vutla <lokeshvutla@ti.com>
To: <linux-omap@vger.kernel.org>
Cc: dsaxena@plexity.net, Lokesh Vutla <lokeshvutla@ti.com>,
herbert@gondor.hengli.com.au, linux-crypto@vger.kernel.org,
mpm@selenic.com, linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] hwrng: OMAP: Updates for OMAP RNG module
Date: Mon, 5 Aug 2013 20:17:17 +0530 [thread overview]
Message-ID: <1375714043-23407-1-git-send-email-lokeshvutla@ti.com> (raw)
This patch series adds support for OMAP4 version of RNG module.
This module produce a 64 bit random number and also allows to
de tune FROs when repeated pattern is coming out of FROs.
This series also has few fixes for the driver.
Lokesh Vutla (6):
hwrng: OMAP: Use module_platform_driver macro
hwrng: OMAP: Convert to devm_kzalloc()
hwrng: OMAP: Remove duplicated function call
hwrng: OMAP: Add device tree support
ARM: OMAP2+: Only manually add hwmod data when DT not used.
hwrng: OMAP: Add OMAP4 TRNG support
arch/arm/mach-omap2/devices.c | 2 +-
drivers/char/hw_random/Kconfig | 6 +-
drivers/char/hw_random/omap-rng.c | 386 ++++++++++++++++++++++++++++++-------
3 files changed, 319 insertions(+), 75 deletions(-)
--
1.7.9.5
next reply other threads:[~2013-08-05 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 14:47 Lokesh Vutla [this message]
2013-08-05 14:47 ` [PATCH 1/6] hwrng: OMAP: Use module_platform_driver macro Lokesh Vutla
2013-08-05 14:47 ` [PATCH 2/6] hwrng: OMAP: Convert to devm_kzalloc() Lokesh Vutla
2013-08-05 14:47 ` [PATCH 3/6] hwrng: OMAP: Remove duplicated function call Lokesh Vutla
2013-08-05 14:47 ` [PATCH 4/6] hwrng: OMAP: Add device tree support Lokesh Vutla
2013-08-05 14:47 ` [PATCH 5/6] ARM: OMAP2+: Only manually add hwmod data when DT not used Lokesh Vutla
2013-08-05 14:47 ` [PATCH 6/6] hwrng: OMAP: Add OMAP4 TRNG support Lokesh Vutla
2013-08-09 6:42 ` [PATCH 0/6] hwrng: OMAP: Updates for OMAP RNG module 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=1375714043-23407-1-git-send-email-lokeshvutla@ti.com \
--to=lokeshvutla@ti.com \
--cc=dsaxena@plexity.net \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mpm@selenic.com \
/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