From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: srinivas.kandagatla@linaro.org, linux-kernel@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org, linux@armlinux.org.uk,
nsaenzjulienne@suse.de, catalin.marinas@arm.com, will@kernel.org,
devicetree@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
robh+dt@kernel.org, bcm-kernel-feedback-list@broadcom.com,
tim.gover@raspberrypi.com, phil@raspberrypi.com
Subject: [PATCH v3 0/5] Expose RPi4's bootloader configuration
Date: Tue, 12 Jan 2021 15:23:37 +0100 [thread overview]
Message-ID: <20210112142342.7290-1-nsaenzjulienne@suse.de> (raw)
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
---
Changes since v2:
- Fix DT bingins
Changes since v1:
- Avoid the reserved-memory indirection by integrating the nvmem driver
into the reserved memory node.
Nicolas Saenz Julienne (5):
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
arm64: defconfig: Enable nvmem's rmem driver
ARM: multi_v7_defconfig: Enable nvmem's rmem driver
.../devicetree/bindings/nvmem/rmem.yaml | 49 ++++++++++
arch/arm/boot/dts/bcm2711-rpi-4-b.dts | 17 ++++
arch/arm/configs/multi_v7_defconfig | 1 +
arch/arm64/configs/defconfig | 1 +
drivers/nvmem/Kconfig | 8 ++
drivers/nvmem/Makefile | 2 +
drivers/nvmem/rmem.c | 97 +++++++++++++++++++
drivers/of/platform.c | 1 +
8 files changed, 176 insertions(+)
create mode 100644 Documentation/devicetree/bindings/nvmem/rmem.yaml
create mode 100644 drivers/nvmem/rmem.c
--
2.29.2
next reply other threads:[~2021-01-12 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 14:23 Nicolas Saenz Julienne [this message]
2021-01-12 14:23 ` [PATCH v3 1/5] dt-bindings: nvmem: Add bindings for rmem driver Nicolas Saenz Julienne
2021-01-14 20:17 ` Rob Herring
2021-01-12 14:23 ` [PATCH v3 2/5] nvmem: Add driver to expose reserved memory as nvmem Nicolas Saenz Julienne
2021-01-12 14:23 ` [PATCH v3 3/5] ARM: dts: bcm2711: Add reserved memory template to hold firmware configuration Nicolas Saenz Julienne
2021-01-12 14:23 ` [PATCH v3 4/5] arm64: defconfig: Enable nvmem's rmem driver Nicolas Saenz Julienne
2021-01-12 14:23 ` [PATCH v3 5/5] ARM: multi_v7_defconfig: " Nicolas Saenz Julienne
2021-01-18 16:50 ` [PATCH v3 0/5] Expose RPi4's bootloader configuration Srinivas Kandagatla
2021-01-25 21:04 ` Nicolas Saenz Julienne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210112142342.7290-1-nsaenzjulienne@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=phil@raspberrypi.com \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=tim.gover@raspberrypi.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).