Re: [PATCH mvebu + mvebu/dt64 4/4] arm64: dts: marvell: armada-37xx: move firmware node to generic dtsi file

[Andrew Lunn <andrew@lunn.ch>]

On Fri, Mar 12, 2021 at 10:10:27AM +0100, Marek Behún wrote:
> On Fri, 12 Mar 2021 09:58:34 +0100
> Gregory CLEMENT <gregory.clement@bootlin.com> wrote:
> 
> > Hello Marek,
> > 
> > > From: Pali Rohár <pali@kernel.org>
> > >
> > > Move the turris-mox-rwtm firmware node from Turris MOX' device tree into
> > > the generic armada-37xx.dtsi file.  
> > 
> > I disagree with this patch. This firmware is specific to Turris MOX so
> > it is not something that should be exposed to all the Armada 3700 based
> > boards.
> > 
> > If you want you still can create an dtsi for this and include it when
> > needed.
> > 
> > Gregory
> 
> Gregory, we are planning to send pull-request for TF-A documentation,
> adding information that people can compile the firmware with CZ.NIC's
> firmware.
> 
> Since this firmware exposes HW random number generator, it is
> possible that people will start using it for espressobin.
> 
> In that case this won't be specific for Turris MOX anymore.

Part of the problem is that it looks specific to the Turris MOX.

But please help me understand the big picture first.  How is the
firmware distributed? Is the binary part of linux-firmware? How does
it get loaded? Does the firmware contain anything which is specific to
the Turris MOX? Could the hardware number generator part be split out
into a more generic sounding name blob?

     Andrew