From: Romain Perier <romain.perier@free-electrons.com>
To: dsaxena@plexity.net, mpm@selenic.com,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: Gregory Clement <gregory.clement@free-electrons.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Nadav Haklai <nadavh@marvell.com>, Omri Itach <omrii@marvell.com>,
Shadi Ammouri <shadi@marvell.com>,
Yahuda Yitschak <yehuday@marvell.com>,
Hanna Hawa <hannah@marvell.com>,
Neta Zur Hershkovits <neta@marvell.com>,
Igal Liberman <igall@marvell.com>,
Marcin Wojtas <mw@semihalf.com>,
linux-crypto@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH v3 0/8] Add support for SafeXcel IP-76 to OMAP RNG
Date: Mon, 26 Sep 2016 12:01:21 +0200 [thread overview]
Message-ID: <57E8F1F1.6040906@free-electrons.com> (raw)
In-Reply-To: <57DBEB1A.4050602@free-electrons.com>
Le 16/09/2016 14:52, Romain Perier a écrit :
> Hello,
>
> Le 16/09/2016 12:08, Romain Perier a écrit :
>> The driver omap-rng has a lot of similarity with the IP block SafeXcel
>> IP-76. A lot of registers are the same and the way that the driver works
>> is very closed the description of the TRNG EIP76 in its datasheet.
>>
>> This series refactorize the driver, add support for generating bigger
>> output random data and add a device variant for SafeXcel IP-76, found
>> in Armada 8K.
>>
>> Romain Perier (8):
>> dt-bindings: Add vendor prefix for INSIDE Secure
>> dt-bindings: omap-rng: Document SafeXcel IP-76 device variant
>> hwrng: omap - Switch to non-obsolete read API implementation
>> hwrng: omap - Remove global definition of hwrng
>> hwrng: omap - Add support for 128-bit output of data
>> hwrng: omap - Don't prefix the probe message with OMAP
>> hwrng: omap - Add device variant for SafeXcel IP-76 found in Armada 8K
>> arm64: dts: marvell: add TRNG description for Armada 8K CP
>>
>> Documentation/devicetree/bindings/rng/omap_rng.txt | 14 +-
>> .../devicetree/bindings/vendor-prefixes.txt | 1 +
>> .../boot/dts/marvell/armada-cp110-master.dtsi | 8 +
>> .../arm64/boot/dts/marvell/armada-cp110-slave.dtsi | 8 +
>> drivers/char/hw_random/Kconfig | 2 +-
>> drivers/char/hw_random/omap-rng.c | 162
>> ++++++++++++++++-----
>> 6 files changed, 152 insertions(+), 43 deletions(-)
>>
>
> If possible, I would like to get "Tested-by" tags by the omap guys
> before this set of patches is merged, to be sure that there are no
> regressions for the OMAP variant.
>
> Thanks,
Added omap ML to Cc:
Romain,
--
Romain Perier, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-26 10:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 10:08 [PATCH v3 0/8] Add support for SafeXcel IP-76 to OMAP RNG Romain Perier
2016-09-16 10:08 ` [PATCH v3 1/8] dt-bindings: Add vendor prefix for INSIDE Secure Romain Perier
2016-09-16 10:08 ` [PATCH v3 2/8] dt-bindings: omap-rng: Document SafeXcel IP-76 device variant Romain Perier
2016-09-16 10:08 ` [PATCH v3 3/8] hwrng: omap - Switch to non-obsolete read API implementation Romain Perier
2016-09-16 10:08 ` [PATCH v3 4/8] hwrng: omap - Remove global definition of hwrng Romain Perier
2016-09-16 10:08 ` [PATCH v3 5/8] hwrng: omap - Add support for 128-bit output of data Romain Perier
2016-09-16 10:08 ` [PATCH v3 6/8] hwrng: omap - Don't prefix the probe message with OMAP Romain Perier
2016-09-16 10:08 ` [PATCH v3 7/8] hwrng: omap - Add device variant for SafeXcel IP-76 found in Armada 8K Romain Perier
2016-09-16 10:08 ` [PATCH v3 8/8] arm64: dts: marvell: add TRNG description for Armada 8K CP Romain Perier
2016-09-16 12:52 ` [PATCH v3 0/8] Add support for SafeXcel IP-76 to OMAP RNG Romain Perier
2016-09-26 10:01 ` Romain Perier [this message]
2016-10-05 20:37 ` Matthijs van Duin
2016-10-20 7:02 ` Romain Perier
2016-10-21 3:10 ` 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=57E8F1F1.6040906@free-electrons.com \
--to=romain.perier@free-electrons.com \
--cc=dsaxena@plexity.net \
--cc=gregory.clement@free-electrons.com \
--cc=hannah@marvell.com \
--cc=herbert@gondor.apana.org.au \
--cc=igall@marvell.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=mw@semihalf.com \
--cc=nadavh@marvell.com \
--cc=neta@marvell.com \
--cc=omrii@marvell.com \
--cc=shadi@marvell.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=yehuday@marvell.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;
as well as URLs for NNTP newsgroup(s).