From: Thierry Reding <thierry.reding@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 2/2] net: eth-uclass: Support device tree MAC addresses
Date: Thu, 25 Apr 2019 15:22:37 +0200 [thread overview]
Message-ID: <20190425132237.GB10218@ulmo> (raw)
In-Reply-To: <CAPnjgZ3-=uLikSZxoWAiAM-7BAKqByrAHvogEUXUZ+3yTBzcwA@mail.gmail.com>
On Wed, Apr 17, 2019 at 09:32:26PM -0700, Simon Glass wrote:
> Hi Thierry,
>
> On Wed, 17 Apr 2019 at 08:03, Thierry Reding <thierry.reding@gmail.com>
> wrote:
>
> > On Wed, Apr 17, 2019 at 02:49:22PM +0300, Grygorii Strashko wrote:
> > >
> > >
> > > On 16.04.19 19:24, Thierry Reding wrote:
> > > > From: Thierry Reding <treding@nvidia.com>
> > > >
> > > > Add the standard Ethernet device tree bindings (imported from v5.0 of
> > > > the Linux kernel) and implement support for reading the MAC address for
> > > > Ethernet devices in the Ethernet uclass. If the "mac-address" property
> > > > exists, the MAC address will be parsed from that. If that property does
> > > > not exist, the "local-mac-address" property will be tried as fallback.
> > > >
> > > > MAC addresses from device tree take precedence over the ones stored in
> > > > a network interface card's ROM.
> > > >
> > > > Acked-by: Joe Hershberger <joe.hershberger@ni.com>
> > > > Signed-off-by: Thierry Reding <treding@nvidia.com>
> > > > ---
> > > > Changes in v2:
> > > > - use dev_read_u8_array_ptr()
> >
>
> It would be good to have test cases for these.
By "these", do you mean the eth_dev_get_mac_address() function that this
patche introduces, or the dev_read_u8_array_ptr() function?
For the former, that'd be a little difficult because it is not a public
API, it's only called from the eth-uclass.c code.
Thierry
> > > >
> > > > .../devicetree/bindings/net/ethernet.txt | 66 +++++++++++++++++++
> > > > net/eth-uclass.c | 26 +++++++-
> > > > 2 files changed, 89 insertions(+), 3 deletions(-)
> > > > create mode 100644 Documentation/devicetree/bindings/net/ethernet.txt
> >
> > Regards,
> Simon
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190425/ee3ab4d0/attachment.sig>
next prev parent reply other threads:[~2019-04-25 13:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 16:24 [U-Boot] [PATCH v2 1/2] net: eth-uclass: Write MAC address to hardware after probe Thierry Reding
2019-04-16 16:24 ` [U-Boot] [PATCH v2 2/2] net: eth-uclass: Support device tree MAC addresses Thierry Reding
2019-04-17 11:49 ` Grygorii Strashko
2019-04-17 15:03 ` Thierry Reding
2019-04-18 4:32 ` Simon Glass
2019-04-25 13:22 ` Thierry Reding [this message]
2019-04-18 16:30 ` Grygorii Strashko
2019-04-25 13:34 ` Thierry Reding
2019-04-16 16:37 ` [U-Boot] [PATCH v2 1/2] net: eth-uclass: Write MAC address to hardware after probe Joe Hershberger
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=20190425132237.GB10218@ulmo \
--to=thierry.reding@gmail.com \
--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