Thread (22 messages) 22 messages, 7 authors, 2019-05-08

Re: [PATCH v4 02/10] dt-bindings: doc: reflect new NVMEM of_get_mac_address behaviour

From: Petr Štetiar <hidden>
Date: 2019-05-08 08:41:59
Also in: linux-arm-kernel, linux-devicetree, linux-mediatek, linux-wireless, lkml

Rob Herring [off-list ref] [2019-05-07 11:44:57]:

Hi,
quoted
-- local-mac-address:   the driver is designed to use the of_get_mac_address api
-                       only if efuse-mac is 0. When efuse-mac is 0, the MAC
-                       address is obtained from local-mac-address. If this
-                       attribute is not present, then the driver will use a
-                       random MAC address.
 - "netcp-device label":        phandle to the device specification for each of NetCP
                        sub-module attached to this interface.

+The MAC address will be determined using the optional properties defined in
+ethernet.txt, as provided by the of_get_mac_address API and only if efuse-mac
Don't make references to Linux in bindings. You can talk about
expectations of client programs (e.g Linux, u-boot, BSD, etc.) though.
I've just tried to reword what was already there, anyway, did I understood
your remark properly, would this be more appropriate?

 The MAC address will be determined using the optional properties defined in
 ethernet.txt and only if efuse-mac is set to 0. If any of the optional MAC
 address properties are not present, then the driver will use random MAC
 address.

Thanks!

-- ynezz
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help