From: "Petr Štetiar" <ynezz@true.cz>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: Maxime Ripard <maxime.ripard@bootlin.com>,
Andy Duan <fugang.duan@nxp.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"john@phrozen.org" <john@phrozen.org>,
"bgolaszewski@baylibre.com" <bgolaszewski@baylibre.com>,
Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Mark Rutland <mark.rutland@arm.com>, Alban Bedel <albeu@free.fr>,
devicetree@vger.kernel.org
Subject: Re: NVMEM address DT post processing [Was: Re: [PATCH net 0/3] add property "nvmem_macaddr_swap" to swap macaddr bytes order]
Date: Mon, 13 May 2019 11:07:00 +0200 [thread overview]
Message-ID: <20190513090700.GW81826@meh.true.cz> (raw)
In-Reply-To: <547abcff-103a-13b8-f42a-c0bd1d910bbc@linaro.org>
Srinivas Kandagatla <srinivas.kandagatla@linaro.org> [2019-05-13 09:25:55]:
Hi,
> My initial idea was to add compatible strings to the cell so that most of
> the encoding information can be derived from it. For example if the encoding
> representing in your example is pretty standard or vendor specific we could
> just do with a simple compatible like below:
that vendor/compatible list would be quite long[1], there are hundreds of
devices in current OpenWrt tree (using currently custom patch) and probably
dozens currently unsupported (ASCII encoded MAC address in NVMEM). So my goal
is to add some DT functionality which would cover all of these.
> eth1_addr: eth-mac-addr@18a {
> compatible = "xxx,nvmem-mac-address";
> reg = <0x18a 0x11>;
> };
while sketching the possible DT use cases I came to the this option as well, it
was very compeling as it would kill two birds with one stone (fix outstanding
MTD/NVMEM OF clash as well[2]), but I think, that it makes more sense to add
this functionality to nvmem core so it could be reused by other consumers, not
just by network layer.
1. https://git.openwrt.org/?p=openwrt%2Fopenwrt.git&a=search&h=HEAD&st=grep&s=mtd-mac-address
2. https://lore.kernel.org/netdev/20190418133646.GA94236@meh.true.cz
-- ynezz
next prev parent reply other threads:[~2019-05-13 9:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 8:23 [PATCH net 0/3] add property "nvmem_macaddr_swap" to swap macaddr bytes order Andy Duan
2019-05-10 8:24 ` [PATCH net 1/3] net: ethernet: " Andy Duan
2019-05-10 18:16 ` Andrew Lunn
2019-05-13 3:10 ` [EXT] " Andy Duan
2019-05-10 8:24 ` [PATCH net 2/3] of_net: add property "nvmem-mac-address" for of_get_mac_addr() Andy Duan
2019-05-10 18:17 ` Andrew Lunn
2019-05-13 3:31 ` [EXT] " Andy Duan
2019-05-13 8:00 ` Petr Štetiar
2019-05-13 8:47 ` Andy Duan
2019-05-10 8:24 ` [PATCH net 3/3] dt-bindings: doc: add new properties for of_get_mac_address from nvmem Andy Duan
2019-05-10 11:28 ` [PATCH net 0/3] add property "nvmem_macaddr_swap" to swap macaddr bytes order Petr Štetiar
2019-05-10 11:31 ` Maxime Ripard
2019-05-10 11:31 ` Maxime Ripard
2019-05-11 14:44 ` NVMEM address DT post processing [Was: Re: [PATCH net 0/3] add property "nvmem_macaddr_swap" to swap macaddr bytes order] Petr Štetiar
2019-05-12 12:19 ` Maxime Ripard
2019-05-12 12:19 ` Maxime Ripard
2019-05-13 9:28 ` Petr Štetiar
2019-05-13 8:25 ` Srinivas Kandagatla
2019-05-13 9:07 ` Petr Štetiar [this message]
2019-05-13 10:06 ` Srinivas Kandagatla
2019-05-13 11:16 ` Petr Štetiar
2019-05-14 15:13 ` Srinivas Kandagatla
2019-05-14 17:44 ` Petr Štetiar
2019-05-15 17:12 ` Srinivas Kandagatla
2019-05-20 14:28 ` Rob Herring
2019-05-13 3:38 ` [EXT] Re: [PATCH net 0/3] add property "nvmem_macaddr_swap" to swap macaddr bytes order Andy Duan
2019-05-13 9:35 ` ynezz
2019-05-13 3:06 ` [EXT] " Andy Duan
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=20190513090700.GW81826@meh.true.cz \
--to=ynezz@true.cz \
--cc=albeu@free.fr \
--cc=andrew@lunn.ch \
--cc=bgolaszewski@baylibre.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=frowand.list@gmail.com \
--cc=fugang.duan@nxp.com \
--cc=hkallweit1@gmail.com \
--cc=john@phrozen.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=srinivas.kandagatla@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.