diff options
author | 2022-02-28 14:12:50 +0100 | |
---|---|---|
committer | 2022-03-23 18:10:00 -0500 | |
commit | 5db1c2dbc04c161d9e6b3f93457452e2ee904bde (patch) | |
tree | 1e1fb92d12595435ba9a14d25e12ef1810b880eb /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | dt-bindings: ufs: qcom: Add SM6350 compatible string (diff) | |
download | wireguard-linux-5db1c2dbc04c161d9e6b3f93457452e2ee904bde.tar.xz wireguard-linux-5db1c2dbc04c161d9e6b3f93457452e2ee904bde.zip |
dt-bindings: nvmem: add U-Boot environment variables binding
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>
Reviewed-by: Tom Rini <trini@konsulko.com>
Signed-off-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20220228131250.16943-1-zajec5@gmail.com
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions