From: "Marek Behún" <kabel@kernel.org>
To: Luka Kovacic <luka.kovacic@sartura.hr>
Cc: "Pali Rohár" <pali@kernel.org>,
"Robert Marko" <robert.marko@sartura.hr>,
U-Boot-Denx <u-boot@lists.denx.de>, "Stefan Roese" <sr@denx.de>,
"Luka Perkov" <luka.perkov@sartura.hr>
Subject: Re: [PATCH 1/2] arm: mvebu: Implement the mac command (Marvell hw_info)
Date: Wed, 13 Oct 2021 16:44:51 +0200 [thread overview]
Message-ID: <20211013164451.2c763e83@dellmb> (raw)
In-Reply-To: <CADZsf3amzcxUf9K1xYxv28opLT5nHfrushRtq53NvOtTdoA7Ew@mail.gmail.com>
On Mon, 11 Oct 2021 18:16:02 +0200
Luka Kovacic <luka.kovacic@sartura.hr> wrote:
>> eth1_mac_addr: eth1addr {
>> compatible = "mac-address-string";
>> name = "eth1addr";
>> };
>
> I don't see any better approach than just matching strings to retrieve
> values for specific keys (for MACs), so this looks good to me.
The `name` property can be omitted, the node name should be used, since
it is unique both in DT and in env.
MAC addresses will need a special compatible property so that the nvmem
driver knows to convert them from 'XX:XX:XX:XX:XX:XX' string to 6-byte
value.
> I agree, a real nvmem API would be much cleaner than the current
> U-Boot implementation, as there is currently no way to
> programmatically access these parameters and the implementations have
> different user interfaces.
>
> As there is currently no nvmem framework, I recommend that the basic,
> futureproof DT bindings are defined and DT parsing is temporarily
> implemented in the hw_info mac command. What do you think?
Yes, that is acceptable.
> Is anyone already working on a nvmem framework to support nvmem
> providers in U-Boot?
AFAIK no, but I am planning to look into this.
In the meantime implement the hw_info mac command.
I will send proposal for dt-binding.
Marek
next prev parent reply other threads:[~2021-10-13 14:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 12:09 [PATCH 1/2] arm: mvebu: Implement the mac command (Marvell hw_info) Robert Marko
2021-10-08 12:09 ` [PATCH 2/2] arm: mvebu: add Globalscale MOCHAbin support Robert Marko
2021-10-08 12:53 ` [PATCH 1/2] arm: mvebu: Implement the mac command (Marvell hw_info) Pali Rohár
2021-10-08 13:28 ` Luka Kovacic
2021-10-08 18:06 ` Pali Rohár
2021-10-09 9:42 ` Marek Behún
2021-10-09 10:09 ` Robert Marko
2021-10-09 10:29 ` Pali Rohár
2021-10-11 10:19 ` Luka Kovacic
2021-10-11 10:56 ` Marek Behún
2021-10-11 16:16 ` Luka Kovacic
2021-10-13 14:44 ` Marek Behún [this message]
2021-10-13 15:35 ` Luka Kovacic
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=20211013164451.2c763e83@dellmb \
--to=kabel@kernel.org \
--cc=luka.kovacic@sartura.hr \
--cc=luka.perkov@sartura.hr \
--cc=pali@kernel.org \
--cc=robert.marko@sartura.hr \
--cc=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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