[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20201215155627.2513-1-nsaenzjulienne@suse.de>
Date: Tue, 15 Dec 2020 16:56:20 +0100
From: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>
To: srinivas.kandagatla@...aro.org,
Saenz Julienne <nsaenzjulienne@...e.de>,
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: [PATCH 0/6] Expose RPi4'd bootloader configuration
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
Powered by blists - more mailing lists