[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <cd1a0145d12a70e89eea7aca49533c56ed24753f.camel@suse.de>
Date: Mon, 25 Jan 2021 22:04:34 +0100
From: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
To: srinivas.kandagatla@...aro.org, linux-kernel@...r.kernel.org
Cc: devicetree@...r.kernel.org, tim.gover@...pberrypi.com,
catalin.marinas@....com, linux@...linux.org.uk, robh+dt@...nel.org,
bcm-kernel-feedback-list@...adcom.com,
linux-arm-kernel@...ts.infradead.org, will@...nel.org,
phil@...pberrypi.com, linux-rpi-kernel@...ts.infradead.org
Subject: Re: [PATCH v3 0/5] Expose RPi4's bootloader configuration
On Tue, 2021-01-12 at 15:23 +0100, Nicolas Saenz Julienne wrote:
> Soon to be released versions of RPi4's firmware will take of care
> passing their bootloader's configuration[1] to the OS by copying it into
> memory and creating a reserved memory node in the board's DT. By
> modeling this reserved memory node as an nvmem device using
> 'nvmem-rmem', which this series introduces, user-space applications will
> be able to query this information through nvmem's sysfs interface.
>
> An alternative approach, less nice IMO, would be to create a
> platform-specific 'soc' driver.
>
> Regards,
> Nicolas
>
> [1] https://www.raspberrypi.org/documentation/hardware/raspberrypi/bcm2711_bootloader_config.md
>
Applied patches #3 to #5 for next.
Regards,
Nicolas
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists