diff options
| author | Rafał Miłecki <[email protected]> | 2023-06-11 15:03:27 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2023-06-15 13:42:17 +0200 |
| commit | bd912c991d2ef079a32558f057b8663bcf1fb6fc (patch) | |
| tree | da782d8cbd50bfa688bc332cdc58ee352944ad25 /tools/perf/scripts/python/flamegraph.py | |
| parent | 08ef7a48ef97fbfd778f02303c565a13bf5bbc3f (diff) | |
dt-bindings: nvmem: layouts: add fixed-layout
With the introduction of NVMEM layouts, new NVMEM content structures
should be defined as such. We should also try to convert / migrate
existing NVMEM content bindings to layouts.
This commit handles fixed NVMEM cells. So far they had to be defined
directly - as device subnodes. With this change it's allowed to put them
in the DT node named "nvmem-layout".
Having NVMEM cells in separated node is preferred as it draws a nice
line between NVMEM device and its content. It results in cleaner
bindings.
FWIW a very similar situation has happened to MTD devices and their
partitions: see commit 5d96ea42eb63 ("dt-bindings: mtd: Clarify all
partition subnodes").
Signed-off-by: Rafał Miłecki <[email protected]>
Reviewed-by: Rob Herring <[email protected]>
Signed-off-by: Srinivas Kandagatla <[email protected]>
Message-ID: <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/flamegraph.py')
0 files changed, 0 insertions, 0 deletions