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
---
Nicolas Saenz Julienne (6):
dt-bindings: nvmem: Add bindings for rmem driver
nvmem: Add driver to expose reserved memory as nvmem
ARM: dts: bcm2711: Add reserved memory template to hold firmware
configuration
ARM: dts: bcm2711: Expose boot-loader configuration
arm64: defconfig: Enable nvmem's rmem driver
ARM: multi_v7_defconfig: Enable nvmem's rmem driver
.../devicetree/bindings/nvmem/rmem.yaml | 35 +++++++
arch/arm/boot/dts/bcm2711-rpi-4-b.dts | 25 +++++
arch/arm/configs/multi_v7_defconfig | 1 +
arch/arm64/configs/defconfig | 1 +
drivers/nvmem/Kconfig | 8 ++
drivers/nvmem/Makefile | 2 +
drivers/nvmem/rmem.c | 92 +++++++++++++++++++
7 files changed, 164 insertions(+)
create mode 100644 Documentation/devicetree/bindings/nvmem/rmem.yaml
create mode 100644 drivers/nvmem/rmem.c
--
2.29.2
