From: PrasannaKumar Muralidharan Subject: Re: [PATCH v3 0/4] crypto: Add driver for JZ4780 PRNG Date: Sat, 25 Nov 2017 20:16:03 +0530 Message-ID: References: <20170918140241.24003-1-prasannatsmkumar@gmail.com> <20171012143011.GA30173@gondor.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Cc: Rob Herring , Ralf Baechle , "David S . Miller" , Paul Cercueil , "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" , linux-mips@linux-mips.org, Mathieu Malaterre , noloader@gmail.com To: Herbert Xu Return-path: Received: from mail-io0-f172.google.com ([209.85.223.172]:46866 "EHLO mail-io0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751631AbdKYOqE (ORCPT ); Sat, 25 Nov 2017 09:46:04 -0500 Received: by mail-io0-f172.google.com with SMTP id q64so19192943iof.13 for ; Sat, 25 Nov 2017 06:46:04 -0800 (PST) In-Reply-To: Sender: linux-crypto-owner@vger.kernel.org List-ID: Hi Ralf, On 12 October 2017 at 22:59, PrasannaKumar Muralidharan wrote: > Hi Herbert, > > On 12 October 2017 at 20:00, Herbert Xu wrote: >> On Mon, Sep 18, 2017 at 07:32:37PM +0530, PrasannaKumar Muralidharan wrote: >>> This patch series adds support of pseudo random number generator found >>> in Ingenic's JZ4780 and X1000 SoC. >>> >>> Create cgublock node which has CGU and RNG node as its children. The >>> cgublock node uses "simple-bus" compatible which helps in exposing CGU >>> and RNG nodes without changing CGU driver. Add 'syscon' compatible in >>> CGU node in jz4780.dtsi. The jz4780-rng driver uses regmap exposed via >>> syscon interface to access the RNG registers. CGU driver is not >>> modified in this patch set as registers used by CGU driver and this >>> driver are different. >>> >>> PrasannaKumar Muralidharan (4): >>> crypto: jz4780-rng: Add JZ4780 PRNG devicetree binding documentation >>> crypto: jz4780-rng: Add Ingenic JZ4780 hardware PRNG driver >>> crypto: jz4780-rng: Add RNG node to jz4780.dtsi >>> crypto: jz4780-rng: Enable PRNG support in CI20 defconfig >> >> Please indicate which patches are intended to go through the crypto >> trees. > > From https://patchwork.linux-mips.org/patch/17162/ I expect the same. > Either all patches go via crypto tree or via mips tree. > The dtsi changes is not yet acked by MIPS / JZ4780 maintainer. Let's > wait for it. > > Thanks, > PrasannaKumar Should I do anything more for this series? Thanks, PrasannaKumar