[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2f4968f856bb8d1181079869c0af6306b5cec8e8.camel@suse.de>
Date: Tue, 15 Dec 2020 17:05:15 +0100
From: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
To: srinivas.kandagatla@...aro.org, devicetree@...r.kernel.org,
bcm-kernel-feedback-list@...adcom.com,
linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org
Cc: linux-kernel@...r.kernel.org, linux@...linux.org.uk,
catalin.marinas@....com, will@...nel.org, robh+dt@...nel.org,
tim.gover@...pberrypi.com, phil@...pberrypi.com
Subject: Re: [PATCH 0/6] Expose RPi4'd bootloader configuration
On Tue, 2020-12-15 at 16:56 +0100, Nicolas Saenz Julienne wrote:
> Soon to be released versions of RPi4's firmware will take of care
> passing their bootloader's configuration to the OS by copying it into
> memory and creating a reserved memory node in the board's DT. In order
> to make use of this information, this series introduces a new generic
> nvmem driver that maps reserved-memory nodes into nvmem devices.
>
> An alternative approach, less nice IMO, would be to create a
> platform-specific 'soc' driver.
>
> Regards,
> Nicolas
There's a typo in the Subject, it should look like this:
'Expose RPi4's bootloader configuration'
Regards,
Nicolas
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists