Hi,
this patch introduce an usual way to getting extended address from device tree.
I added the properties "extended-address" and "local-extended-address". The
ethernet framework has "mac-address", "local-mac-address" and "address", where
"address" is according the comment an obsolete property.
An example how you could add a extended address would be:
&spi1 {
status = "okay";
pinctrl-names = "default";
pinctrl-0 = <&spi1_pins>;
at86rf231@0 {
compatible = "atmel,at86rf231";
spi-max-frequency = <7500000>;
reg = <0>;
interrupts = <19 4>;
interrupt-parent = <&gpio3>;
xtal-trim = /bits/ 8 <0x03>;
extended-address = [ DE AD BE EF CA FE FA CE ];
};
};
This is actually a RFC only. I want to be sure that we can use this naming
convention and I need also add a cc in Patch 1/1 ("of: net: add support for
extended address") to the device tree mailinglist, then wait for an acked-by
and marcel can apply it on bluetooth-next and we have it mainline.
- Alex
Alexander Aring (2):
of: net: add support for extended address
at86rf230: add support for dt or pdata extended addr
drivers/net/ieee802154/at86rf230.c | 15 ++++++++++++---
drivers/of/of_net.c | 34 ++++++++++++++++++++++++++++++++++
include/linux/of_net.h | 6 ++++++
include/linux/spi/at86rf230.h | 1 +
4 files changed, 53 insertions(+), 3 deletions(-)
--
2.3.0
--
To unsubscribe from this list: send the line "unsubscribe linux-wpan" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
