Currently, of_get_mac_address supports NVMEM, some platforms MAC address that read from NVMEM efuse requires to swap bytes order, so add new property "nvmem_macaddr_swap" to specify the behavior. If the MAC address is valid from NVMEM, add new property "nvmem-mac-address" in ethernet node.
Update these two properties in the binding documentation. Signed-off-by: Fugang Duan <fugang.d...@nxp.com> --- Documentation/devicetree/bindings/net/ethernet.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Documentation/devicetree/bindings/net/ethernet.txt b/Documentation/devicetree/bindings/net/ethernet.txt index e88c364..921364a 100644 --- a/Documentation/devicetree/bindings/net/ethernet.txt +++ b/Documentation/devicetree/bindings/net/ethernet.txt @@ -10,8 +10,11 @@ Documentation/devicetree/bindings/phy/phy-bindings.txt. property; - local-mac-address: array of 6 bytes, specifies the MAC address that was assigned to the network device; +- nvmem-mac-address: array of 6 bytes, specifies the MAC address that was + read from nvmem-cells and dynamically add the property in device node; - nvmem-cells: phandle, reference to an nvmem node for the MAC address - nvmem-cell-names: string, should be "mac-address" if nvmem is to be used +- nvmem_macaddr_swap: swap bytes order for the 6 bytes of MAC address - max-speed: number, specifies maximum speed in Mbit/s supported by the device; - max-frame-size: number, maximum transfer unit (IEEE defined MTU), rather than the maximum frame size (there's contradiction in the Devicetree -- 2.7.4
