Skip to content

Commit

Permalink
dt-bindings: nvmem: brcm,nvram: add basic NVMEM cells
Browse files Browse the repository at this point in the history
NVRAM doesn't have cells at hardcoded addresses. They are stored in
internal struct (custom & dynamic format). It's still important to
define relevant cells in DT so NVMEM consumers can reference them.

Update binding to allow including basic cells as NVMEM device subnodes.

Reviewed-by: Rob Herring <robh@kernel.org>
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Link: https://lore.kernel.org/r/20220225175822.8293-5-srinivas.kandagatla@linaro.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
  • Loading branch information
Rafał Miłecki authored and Greg Kroah-Hartman committed Mar 18, 2022
1 parent 82a05d8 commit 084973e
Showing 1 changed file with 23 additions and 2 deletions.
25 changes: 23 additions & 2 deletions Documentation/devicetree/bindings/nvmem/brcm,nvram.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,8 @@ description: |
NVRAM can be accessed on Broadcom BCM47xx MIPS and Northstar ARM Cortex-A9
devices usiong I/O mapped memory.
NVRAM variables can be defined as NVMEM device subnodes.
maintainers:
- Rafał Miłecki <rafal@milecki.pl>

Expand All @@ -27,11 +29,30 @@ properties:
reg:
maxItems: 1

board_id:
type: object
description: Board identification name

et0macaddr:
type: object
description: First Ethernet interface's MAC address

et1macaddr:
type: object
description: Second Ethernet interface's MAC address

et2macaddr:
type: object
description: Third Ethernet interface's MAC address

unevaluatedProperties: false

examples:
- |
nvram@1eff0000 {
compatible = "brcm,nvram";
reg = <0x1eff0000 0x10000>;
compatible = "brcm,nvram";
reg = <0x1eff0000 0x10000>;
mac: et0macaddr {
};
};

0 comments on commit 084973e

Please sign in to comment.