From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: [RFC] ARM: omap3: Enable HWMODS for HW Random Number Generator Date: Mon, 9 Sep 2019 09:35:43 -0700 Message-ID: <20190909163543.GQ52127@atomide.com> References: <20190828150037.2640-1-aford173@gmail.com> <20190905230443.GA52127@atomide.com> <20190909134033.s26eiurpat3iekse@pali> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Content-Disposition: inline In-Reply-To: <20190909134033.s26eiurpat3iekse@pali> Sender: linux-kernel-owner@vger.kernel.org To: Pali =?utf-8?B?Um9ow6Fy?= Cc: Adam Ford , Linux-OMAP , Tero Kristo , Aaro Koskinen , Adam Ford , =?utf-8?Q?Beno=C3=AEt?= Cousson , Rob Herring , Mark Rutland , Russell King , Paul Walmsley , devicetree , Linux Kernel Mailing List , arm-soc List-Id: devicetree@vger.kernel.org * Pali Rohár [190909 13:41]: > On Monday 09 September 2019 08:37:09 Adam Ford wrote: > > I applied this on 5.3 and it is working. I assume the same is true in for-next. Hmm I noticed I stopped getting RNG data after several rmmod modprobe cycles, or several hd /dev/random reads. Anybody else seeing that? > > Do you want to submit a formal patch? I can mark it as 'tested-by' > > This really helps speed up the startup sequence on boards with sshd > > because it delays for nearly 80 seconds waiting for entropy without > > the hwrng. > > Hi! When applying a patch, could you please disable this rng for n900? > > In omap3-n900.dts for rng should be status = "disabled" (as Tony already > wrote), similarly like for aes. Yeah I'll post a proper patch after -rc1. Regards, Tony