[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1e0ad098ca7b1c13dbc6602285b77790b9cd54a1.camel@suse.de>
Date: Tue, 15 Dec 2020 20:01:54 +0100
From: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
To: Catalin Marinas <catalin.marinas@....com>
Cc: 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, linux-kernel@...r.kernel.org,
linux@...linux.org.uk, will@...nel.org, robh+dt@...nel.org,
tim.gover@...pberrypi.com, phil@...pberrypi.com
Subject: Re: [PATCH 0/6] Expose RPi4'd bootloader configuration
Hi Catalin,
On Tue, 2020-12-15 at 18:44 +0000, Catalin Marinas wrote:
> On Tue, Dec 15, 2020 at 04:56:20PM +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.
>
> What kind of information is this and how would the kernel use it?
Sorry, I wasn't clear enough, the ultimate goal is to use this information from
user-space, through nvmem's sysfs interface. The kernel itself has no use for
it.
Regards,
Nicolas
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists