All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
	Florian Fainelli <f.fainelli@gmail.com>
Cc: Stephen Brennan <stephen@brennan.io>,
	Matt Mackall <mpm@selenic.com>, Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>, Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	bcm-kernel-feedback-list@broadcom.com,
	Eric Anholt <eric@anholt.net>, Stefan Wahren <wahrenst@gmx.net>,
	Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH v3 0/4] Raspberry Pi 4 HWRNG Support
Date: Tue, 3 Dec 2019 20:55:04 -0800	[thread overview]
Message-ID: <5beb190c-fa77-6693-aead-4030930f5b8a@gmail.com> (raw)
In-Reply-To: <20191121053046.coobocevp4uwwugb@gondor.apana.org.au>



On 11/20/2019 9:30 PM, Herbert Xu wrote:
> On Wed, Nov 20, 2019 at 08:09:57PM -0800, Florian Fainelli wrote:
>> Hi Herbert,
>>
>> On 11/19/2019 7:16 PM, Stephen Brennan wrote:
>>> 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.
>>
>> When we get a review from Rob, you can take patches 1-2 through your
>> tree and Stefan/Nicholas can queue patches 3-4 through the BCM2835 tree
>> where the DTS files already exist. Does that work for you?
> 
> Yes sure.

Rob has provided his Acked-by for the binding patch, are you targeting
these changes for 5.5 or 5.6 at this point?
-- 
Florian

WARNING: multiple messages have this Message-ID (diff)
From: Florian Fainelli <f.fainelli@gmail.com>
To: Herbert Xu <herbert@gondor.apana.org.au>,
	Florian Fainelli <f.fainelli@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
	Arnd Bergmann <arnd@arndb.de>,
	Scott Branden <sbranden@broadcom.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Ray Jui <rjui@broadcom.com>,
	linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
	Eric Anholt <eric@anholt.net>, Rob Herring <robh+dt@kernel.org>,
	bcm-kernel-feedback-list@broadcom.com,
	Stephen Brennan <stephen@brennan.io>,
	Matt Mackall <mpm@selenic.com>,
	linux-arm-kernel@lists.infradead.org,
	Stefan Wahren <wahrenst@gmx.net>
Subject: Re: [PATCH v3 0/4] Raspberry Pi 4 HWRNG Support
Date: Tue, 3 Dec 2019 20:55:04 -0800	[thread overview]
Message-ID: <5beb190c-fa77-6693-aead-4030930f5b8a@gmail.com> (raw)
In-Reply-To: <20191121053046.coobocevp4uwwugb@gondor.apana.org.au>



On 11/20/2019 9:30 PM, Herbert Xu wrote:
> On Wed, Nov 20, 2019 at 08:09:57PM -0800, Florian Fainelli wrote:
>> Hi Herbert,
>>
>> On 11/19/2019 7:16 PM, Stephen Brennan wrote:
>>> 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.
>>
>> When we get a review from Rob, you can take patches 1-2 through your
>> tree and Stefan/Nicholas can queue patches 3-4 through the BCM2835 tree
>> where the DTS files already exist. Does that work for you?
> 
> Yes sure.

Rob has provided his Acked-by for the binding patch, are you targeting
these changes for 5.5 or 5.6 at this point?
-- 
Florian

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-12-04  4:55 UTC|newest]

Thread overview: 44+ 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 ` Stephen Brennan
2019-11-20  3:16 ` [PATCH v3 1/4] dt-bindings: rng: add BCM2711 RNG compatible Stephen Brennan
2019-11-20  3:16   ` Stephen Brennan
2019-11-20  4:50   ` Baruch Siach
2019-11-20  4:50     ` Baruch Siach
2019-11-20  5:21     ` Stephen Brennan
2019-11-20  5:21       ` Stephen Brennan
2019-11-20 19:55   ` Florian Fainelli
2019-11-20 19:55     ` Florian Fainelli
2019-11-23  0:39   ` Rob Herring
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  3:16   ` Stephen Brennan
2019-11-20  4:52   ` Baruch Siach
2019-11-20  4:52     ` Baruch Siach
2019-11-20 17:33     ` Matthias Brugger
2019-11-20 17:33       ` Matthias Brugger
2019-11-20 19:55   ` Florian Fainelli
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  3:16   ` Stephen Brennan
2019-11-20 16:20   ` Stefan Wahren
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  3:16   ` Stephen Brennan
2019-11-20 16:21   ` Stefan Wahren
2019-11-20 16:21     ` Stefan Wahren
2019-11-20 19:45   ` Nicolas Saenz Julienne
2019-11-20 19:45     ` Nicolas Saenz Julienne
2019-11-20 16:16 ` [PATCH v3 0/4] Raspberry Pi 4 HWRNG Support Stefan Wahren
2019-11-20 16:16   ` Stefan Wahren
2019-11-20 19:50   ` Nicolas Saenz Julienne
2019-11-20 19:50     ` Nicolas Saenz Julienne
2019-11-21 10:14     ` Stefan Wahren
2019-11-21 10:14       ` Stefan Wahren
2019-11-21  4:09 ` Florian Fainelli
2019-11-21  4:09   ` Florian Fainelli
2019-11-21  5:30   ` Herbert Xu
2019-11-21  5:30     ` Herbert Xu
2019-12-04  4:55     ` Florian Fainelli [this message]
2019-12-04  4:55       ` Florian Fainelli
2019-12-04  4:59       ` Herbert Xu
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=5beb190c-fa77-6693-aead-4030930f5b8a@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=eric@anholt.net \
    --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 \
    --cc=wahrenst@gmx.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.