On Mon, Feb 28, 2022 at 02:12:50PM +0100, Rafał Miłecki wrote:
From: Rafał Miłecki rafal@milecki.pl
U-Boot uses environment variables for storing device setup data. It usually needs to be accessed by a bootloader, kernel and often user-space.
This binding allows describing environment data located in a raw flash partition. It's treated as NVMEM device and can be reused later for other storage devices.
Using DT should be cleaner than hardcoding & duplicating such info in multiple places. Bootloader & kernel can share DTS and user-space can try reading it too or just have correct data exposed by a kernel.
A custom "compatible" string allows system to automatically load relevant NVMEM driver but phandle can be also used for reading raw location.
Signed-off-by: Rafał Miłecki rafal@milecki.pl
V2: Update descriptions to don't make this binding MTD (flash partition) specific. Mention multiple possible storage ways. V3: Drop allOf: - $ref: nvmem.yaml# as we don't use anything rom the nvmem.yaml. Thanks Rob.
.../devicetree/bindings/nvmem/u-boot,env.yaml | 62 +++++++++++++++++++ MAINTAINERS | 5 ++ 2 files changed, 67 insertions(+) create mode 100644 Documentation/devicetree/bindings/nvmem/u-boot,env.yaml
A u-boot maintainer should ack this.
Rob