Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: James Hogan <jhogan@kernel.org>
To: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>
Cc: herbert@gondor.apana.org.au, robh+dt@kernel.org,
	ralf@linux-mips.org, davem@davemloft.net, paul@crapouillou.net,
	linux-crypto@vger.kernel.org, linux-mips@linux-mips.org,
	malat@debian.org, noloader@gmail.com
Subject: Re: [PATCH v3 3/4] crypto: jz4780-rng: Add RNG node to jz4780.dtsi
Date: Tue, 6 Mar 2018 09:32:37 +0000	[thread overview]
Message-ID: <20180306091932.GM4197@saruman> (raw)
In-Reply-To: <20170918140241.24003-4-prasannatsmkumar@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 681 bytes --]

On Mon, Sep 18, 2017 at 07:32:40PM +0530, PrasannaKumar Muralidharan wrote:
> Add RNG node to jz4780 dtsi. This driver uses registers that are part of
> the register set used by Ingenic CGU driver. Use regmap in RNG driver to
> access its register. Create 'simple-bus' node, make CGU and RNG node as
> child of it so that both the nodes are visible without changing CGU
> driver code.
> 
> Signed-off-by: PrasannaKumar Muralidharan <prasannatsmkumar@gmail.com>

Better late than never:
Acked-by: James Hogan <jhogan@kernel.org>

(I presume its okay for the reg ranges to overlap, ISTR that being an
issue a few years ago, but maybe thats fixed now).

Cheers
James

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2018-03-06  9:33 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-18 14:02 [PATCH v3 0/4] crypto: Add driver for JZ4780 PRNG PrasannaKumar Muralidharan
2017-09-18 14:02 ` [PATCH v3 1/4] crypto: jz4780-rng: Add JZ4780 PRNG devicetree binding documentation PrasannaKumar Muralidharan
2017-09-18 14:02 ` [PATCH v3 2/4] crypto: jz4780-rng: Add Ingenic JZ4780 hardware PRNG driver PrasannaKumar Muralidharan
2017-09-18 14:02 ` [PATCH v3 3/4] crypto: jz4780-rng: Add RNG node to jz4780.dtsi PrasannaKumar Muralidharan
2018-03-06  9:32   ` James Hogan [this message]
2018-03-06 13:55     ` Rob Herring
2018-03-06 13:55       ` Rob Herring
2018-03-07 14:54       ` PrasannaKumar Muralidharan
2018-03-07 14:54         ` PrasannaKumar Muralidharan
2018-03-07 20:25         ` Rob Herring
2018-03-07 20:25           ` Rob Herring
2018-03-06 23:01     ` [PATCH v3 3/4] crypto: jz4780-rng: Add RNG node to jz4780.dtsi, Paul Cercueil
2018-03-07 14:51       ` [PATCH v3 3/4] crypto: jz4780-rng: Add RNG node to jz4780.dtsi PrasannaKumar Muralidharan
2018-03-07 14:51         ` PrasannaKumar Muralidharan
2018-03-07 20:23         ` [PATCH v3 3/4] crypto: jz4780-rng: Add RNG node to jz4780.dtsi, Paul Cercueil
2018-03-07 20:23           ` Paul Cercueil
2017-09-18 14:02 ` [PATCH v3 4/4] crypto: jz4780-rng: Enable PRNG support in CI20 defconfig PrasannaKumar Muralidharan
2017-10-12 14:30 ` [PATCH v3 0/4] crypto: Add driver for JZ4780 PRNG Herbert Xu
2017-10-12 17:29   ` PrasannaKumar Muralidharan
2017-10-12 17:29     ` PrasannaKumar Muralidharan
2017-11-25 14:46     ` PrasannaKumar Muralidharan
2017-11-25 14:46       ` PrasannaKumar Muralidharan

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=20180306091932.GM4197@saruman \
    --to=jhogan@kernel.org \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=malat@debian.org \
    --cc=noloader@gmail.com \
    --cc=paul@crapouillou.net \
    --cc=prasannatsmkumar@gmail.com \
    --cc=ralf@linux-mips.org \
    --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