From: "Andrew Jeffery" <andrew@aj.id.au>
To: "Oscar A Perez" <linux@neuralgames.com>
Cc: "Joel Stanley" <joel@jms.id.au>, "Matt Mackall" <mpm@selenic.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Linux Crypto Mailing List" <linux-crypto@vger.kernel.org>,
devicetree <devicetree@vger.kernel.org>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
linux-aspeed <linux-aspeed@lists.ozlabs.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] hwrng: Add support for ASPEED RNG
Date: Mon, 03 Feb 2020 14:37:16 +1030 [thread overview]
Message-ID: <f6beee98-360c-4239-ab01-86ba41629f9b@www.fastmail.com> (raw)
In-Reply-To: <27c5505acd8d09f70ec9cd12982b2e3e@neuralgames.com>
On Wed, 29 Jan 2020, at 10:56, linux@neuralgames.com wrote:
> On 2020-01-27 18:53, Andrew Jeffery wrote:
> > Not that I've looked, but is it feasible to augment timeriomem-rng with
> > the ability to configure the RNG rather than implement a new driver?
> > Why
> > didn't you go that route?
> >
>
> I decided to wrote the Aspeed-RNG driver because was under the
> impression that the community would prefer dedicated drivers over
> generic ones for these SOCs.
I think we should leverage existing work where we can. Lets not make
more extra for ourselves :)
> However, enhancing timeriomem-rng module
> is not hard at all. As I matter of fact, I'm currently testing changes
> to timeriomem-rng and so far so good. If you would like to have a quick
> look to my changes, I just pushed patches to the same repo a couple of
> hours ago:
> https://github.com/operezmuena/aspeed-rng-testing/tree/master/patches
I think this is a good approach so long as we can create a clean interface
to the control MMIO(s) inside the driver, i.e. we shouldn't be baking any
Aspeed-specific information into generic sections of code. Usually this
means sticking a pointer to an ops struct in the data member of the
matching OF ID struct.
Input from the RNG maintainers will be helpful here.
Andrew
next prev parent reply other threads:[~2020-02-03 4:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 15:01 [PATCH 1/2] hwrng: Add support for ASPEED RNG Oscar A Perez
2020-01-20 15:01 ` [PATCH 2/2] " Oscar A Perez
2020-01-20 19:21 ` kbuild test robot
2020-01-21 1:53 ` [PATCH 1/2] " Joel Stanley
2020-01-23 1:25 ` linux
2020-01-23 1:53 ` Andrew Jeffery
2020-01-25 1:10 ` linux
2020-01-28 0:53 ` Andrew Jeffery
2020-01-29 0:26 ` linux
2020-02-03 4:07 ` Andrew Jeffery [this message]
2020-02-03 4:09 ` Andrew Jeffery
2020-02-03 10:31 ` Rob Herring
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=f6beee98-360c-4239-ab01-86ba41629f9b@www.fastmail.com \
--to=andrew@aj.id.au \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@neuralgames.com \
--cc=mark.rutland@arm.com \
--cc=mpm@selenic.com \
--cc=robh+dt@kernel.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).