[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190910143732.3g3q4acvnx2pqvjx@earth.universe>
Date: Tue, 10 Sep 2019 15:37:32 +0100
From: Sebastian Reichel <sre@...nel.org>
To: Adam Ford <aford173@...il.com>
Cc: Tony Lindgren <tony@...mide.com>,
Mark Rutland <mark.rutland@....com>,
devicetree <devicetree@...r.kernel.org>,
Paul Walmsley <paul@...an.com>,
Aaro Koskinen <aaro.koskinen@....fi>,
Russell King <linux@...linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Tero Kristo <t-kristo@...com>,
Rob Herring <robh+dt@...nel.org>,
Benoît Cousson <bcousson@...libre.com>,
Pali Rohár <pali.rohar@...il.com>,
Linux-OMAP <linux-omap@...r.kernel.org>,
Adam Ford <adam.ford@...icpd.com>,
arm-soc <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [RFC] ARM: omap3: Enable HWMODS for HW Random Number Generator
Hi,
On Tue, Sep 10, 2019 at 08:56:49AM -0500, Adam Ford wrote:
> On Thu, Sep 5, 2019 at 6:04 PM Tony Lindgren <tony@...mide.com> wrote:
> > Oh and this needs to default to status = "disabled" for
> > HS devices like n900 as it needs to use the omap3-rom-rng.
>
> I don't know enough about the HS version of the OMAP3, but what's the
> main difference between omap3-rom-rng and this one?
The OMAP HS chips have the bus firewall configured to block direct
access to some cryptography related devices. The kernel will crash
with a bus error, if you try to read/write the registers for
protected devices. The omap3-rom-rng avoids this by communicating
with the security middleware component instead of directly accessing
the RNG hardware.
-- Sebastian
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists