* Adam Ford <aford173@xxxxxxxxx> [190827 13:18]:
> On Tue, Aug 27, 2019 at 3:12 AM Pali Rohár <pali.rohar@xxxxxxxxx> wrote:
> >
> > On Monday 26 August 2019 11:00:21 Tero Kristo wrote:
> > > On 24.8.2019 0.46, Aaro Koskinen wrote:
> > > > Hi,
> > > >
> > > > I was looking at N900 boot logs from the current mainline (v5.3-rc),
> > > > and noticed this:
> > > >
> > > > [ 3.297668] omap3_rom_rng: initializing
> > > > [ 3.301940] omap3_rom_rng: unable to get RNG clock
> > > > [ 3.307006] omap3-rom-rng: probe of omap3-rom-rng failed with error -2
> > > >
> > > > It seems some clock data was deleted with 0ed266d7ae5e ("clk: ti: omap3:
> > > > cleanup unnecessary clock aliases"), including one for omap3-rom-rng.
> > > > How this driver is supposed to work now? I guess it has been broken for
> > > > a while. :-(
> > >
> > > You should have a DT node for the device, which contains the clock handle.
>
> I am interested in enabling the RNG too, because sshd takes a long
> time to initialize without the hwrng.
FYI, I'll be posting some fixes to omap3_rom_rng including
the dts support. Not getting any data from it yet though..
Regards,
Tony
