archive mirror
 help / color / mirror / Atom feed
From: Michael Walle <>
	Srinivas Kandagatla <>,
	Michael Walle <>
Subject: Re: [PATCH] of: net: support NVMEM cells with MAC in text format
Date: Wed, 29 Dec 2021 13:40:47 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


> Some NVMEM devices have text based cells. In such cases MAC is stored in
> a XX:XX:XX:XX:XX:XX format. Use mac_pton() to parse such data and
> support those NVMEM cells. This is required to support e.g. a very
> popular U-Boot and its environment variables.
> Signed-off-by: Rafał Miłecki <>
> ---
> Please let me know if checking NVMEM cell length (6 B vs. 17 B) can be
> considered a good enough solution. Alternatively we could use some DT
> property to make it explicity, e.g. something like:
> ethernet@18024000 {
> 	compatible = "brcm,amac";
> 	reg = <0x18024000 0x800>;
> 	nvmem-cells = <&mac_addr>;
> 	nvmem-cell-names = "mac-address";
> 	nvmem-mac-format = "text";
> };

Please note, that there is also this proposal, which had such a conversion
in mind:

With this patch, there are now two different places where a mac address
format is converted. In of_get_mac_addr_nvmem() and in the imx otp driver.
And both have their shortcomings and aren't really flexible. Eg. this one
magically detects the format by comparing the length, but can't be used for
to swap bytes (because the length is also ETH_ALEN), which apparently is a
use case in the imx otp driver. And having the conversion in an nvmem
provider device driver is still a bad thing IMHO.

I'd really like to see all these kind of transformations in one place.


  parent reply	other threads:[~2021-12-29 12:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 12:27 [PATCH] of: net: support NVMEM cells with MAC in text format Rafał Miłecki
2021-12-29 11:40 ` patchwork-bot+netdevbpf
2021-12-29 12:40 ` Michael Walle [this message]
2021-12-29 18:18   ` Jakub Kicinski
2021-12-29 22:04     ` Michael Walle
2022-01-06  9:23   ` Michael Walle

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).