From: Sascha Hauer <s.hauer@pengutronix.de>
To: Andrey Smirnov <andrew.smirnov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [RFC 1/2] misc: Add MAC address mapper "driver"
Date: Mon, 1 Feb 2016 11:10:07 +0100 [thread overview]
Message-ID: <20160201101007.GA4118@pengutronix.de> (raw)
In-Reply-To: <1454306234-2299-1-git-send-email-andrew.smirnov@gmail.com>
On Sun, Jan 31, 2016 at 09:57:13PM -0800, Andrey Smirnov wrote:
> Add Barebox specific device tree provisions to allow specifying MAC
> addresses for network interfaces via device tree.
>
> Signed-off-by: Andrey Smirnov <andrew.smirnov@gmail.com>
> ---
> .../bindings/barebox/barebox,mac-address-map.rst | 27 ++++
> drivers/misc/Makefile | 1 +
> drivers/misc/mac-address-map.c | 142 +++++++++++++++++++++
> 3 files changed, 170 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/barebox/barebox,mac-address-map.rst
> create mode 100644 drivers/misc/mac-address-map.c
>
> diff --git a/Documentation/devicetree/bindings/barebox/barebox,mac-address-map.rst b/Documentation/devicetree/bindings/barebox/barebox,mac-address-map.rst
> new file mode 100644
> index 0000000..1ac3062
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/barebox/barebox,mac-address-map.rst
> @@ -0,0 +1,27 @@
> +barebox MAC address map
> +=======================
> +
> +This driver allows to specify each network adapter's source of MAC address from the devicetree.
> +
> +Required properties:
> +
> +* ``compatible``: should be ``barebox,mac-address-map``
> +
> +Besides ``compatible`` property the node is expected to contain a
> +number of children nodes each specifing a single "MAC source ->
> +interface" mapping.
> +
> +Child node's required properties:
> +* ``network-interface``: phandle corresponding to network interface
> +* ``mac-location``: a pair of phandle to 'cdev' containing MAC address
> + and offset withing that 'cdev'
> +
> +Example::
> +
> + mac-address-map {
> + compatible = "barebox,mac-address-map";
> + nic@0 {
> + network-interface = <&fec>;
> + mac-location = <&ocotp 0x88>;
> + };
> + };
I wonder if the correct way to do this wouldn't be nvmem, see
Documentation/devicetree/bindings/nvmem/nvmem.txt in the Kernel.
This would mandate a binding like:
ocotp {
mac1: mac@88 {
reg = <0x88 0x6>;
};
};
&fec {
nvmem-cells = <&mac1>;
nvmem-cell-names = "mac-address";
};
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2016-02-01 10:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 5:57 Andrey Smirnov
2016-02-01 5:57 ` [RFC 2/2] arm/dts: i.MX6: Use generic MAC address mapper Andrey Smirnov
2016-02-01 10:10 ` Sascha Hauer [this message]
2016-02-01 19:18 ` [RFC 1/2] misc: Add MAC address mapper "driver" Trent Piepho
2016-02-03 1:14 ` Andrey Smirnov
2016-02-03 18:40 ` Trent Piepho
2016-02-03 20:16 ` Andrey Smirnov
2016-02-03 1:09 ` Andrey Smirnov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160201101007.GA4118@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=andrew.smirnov@gmail.com \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox