devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Wahren <wahrenst@gmx.net>
To: Stephen Brennan <stephen@brennan.io>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
	Florian Fainelli <f.fainelli@gmail.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	Scott Branden <sbranden@broadcom.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-arm-kernel@lists.infradead.org, Ray Jui <rjui@broadcom.com>,
	linux-kernel@vger.kernel.org, Eric Anholt <eric@anholt.net>,
	Rob Herring <robh+dt@kernel.org>,
	bcm-kernel-feedback-list@broadcom.com,
	Stefan Wahren <wahrenst@gmx.net>, Matt Mackall <mpm@selenic.com>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-crypto@vger.kernel.org
Subject: Re: [PATCH v3 0/4] Raspberry Pi 4 HWRNG Support
Date: Wed, 20 Nov 2019 17:16:47 +0100	[thread overview]
Message-ID: <99554159-6abb-6ea5-aebb-57a148a59b78@gmx.net> (raw)
In-Reply-To: <20191120031622.88949-1-stephen@brennan.io>

Hi Stephen,

Am 20.11.19 um 04:16 schrieb Stephen Brennan:
> This patch series enables support for the HWRNG included on the Raspberry
> Pi 4.  It is simply a rebase of Stefan's branch [1]. I went ahead and
> tested this out on a Pi 4.  Prior to this patch series, attempting to use
> the hwrng gives:
>
>     $ head -c 2 /dev/hwrng
>     head: /dev/hwrng: Input/output error
>
> After this series, the same command gives two random bytes.

just a note: a more expressive test would be running rngtest (package
rng-tools) on this device.

Regards
Stefan



  parent reply	other threads:[~2019-11-20 16:17 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20  3:16 [PATCH v3 0/4] Raspberry Pi 4 HWRNG Support Stephen Brennan
2019-11-20  3:16 ` [PATCH v3 1/4] dt-bindings: rng: add BCM2711 RNG compatible Stephen Brennan
2019-11-20  4:50   ` Baruch Siach
2019-11-20  5:21     ` Stephen Brennan
2019-11-20 19:55   ` Florian Fainelli
2019-11-23  0:39   ` Rob Herring
2019-11-20  3:16 ` [PATCH v3 2/4] hwrng: iproc-rng200: Add support for BCM2711 Stephen Brennan
2019-11-20  4:52   ` Baruch Siach
2019-11-20 17:33     ` Matthias Brugger
2019-11-20 19:55   ` Florian Fainelli
2019-11-20  3:16 ` [PATCH v3 3/4] ARM: dts: bcm2835: Move rng definition to common location Stephen Brennan
2019-11-20 16:20   ` Stefan Wahren
2019-11-20  3:16 ` [PATCH v3 4/4] ARM: dts: bcm2711: Enable HWRNG support Stephen Brennan
2019-11-20 16:21   ` Stefan Wahren
2019-11-20 19:45   ` Nicolas Saenz Julienne
2019-11-20 16:16 ` Stefan Wahren [this message]
2019-11-20 19:50   ` [PATCH v3 0/4] Raspberry Pi 4 HWRNG Support Nicolas Saenz Julienne
2019-11-21 10:14     ` Stefan Wahren
2019-11-21  4:09 ` Florian Fainelli
2019-11-21  5:30   ` Herbert Xu
2019-12-04  4:55     ` Florian Fainelli
2019-12-04  4:59       ` 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=99554159-6abb-6ea5-aebb-57a148a59b78@gmx.net \
    --to=wahrenst@gmx.net \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=eric@anholt.net \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=mpm@selenic.com \
    --cc=rjui@broadcom.com \
    --cc=robh+dt@kernel.org \
    --cc=sbranden@broadcom.com \
    --cc=stephen@brennan.io \
    /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).