From: Michael Walle <michael@walle.cc>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 2/2] of: net: fix of_get_mac_addr_nvmem() for PCI and DSA nodes
Date: Mon, 05 Apr 2021 23:46:04 +0200 [thread overview]
Message-ID: <2d6eef78762562bcbb732179b32f0fd9@walle.cc> (raw)
In-Reply-To: <YGuCblk9vvmD0NiH@lunn.ch>
Hi Andrew,
Am 2021-04-05 23:34, schrieb Andrew Lunn:
>> -static int of_get_mac_addr_nvmem(struct device_node *np, u8 addr)
>> +static int of_get_mac_addr_nvmem(struct device_node *np, u8 *addr)
>> {
>> struct platform_device *pdev = of_find_device_by_node(np);
>> + struct nvmem_cell *cell;
>> + const void *mac;
>> + size_t len;
>> int ret;
>>
>> - if (!pdev)
>> - return -ENODEV;
>> + /* Try lookup by device first, there might be a nvmem_cell_lookup
>> + * associated with a given device.
>> + */
>> + if (pdev) {
>> + ret = nvmem_get_mac_address(&pdev->dev, addr);
>> + put_device(&pdev->dev);
>> + return ret;
>> + }
>
> Can you think of any odd corner case where nvmem_get_mac_address()
> would fail, but of_nvmem_cell_get(np, "mac-address") would work?
You mean, it might make sense to just return here when
nvmem_get_mac_address() will succeed and fall back to the
of_nvmem_cell_get() in case of an error?
nvmem_get_mac_address() will first try to do the lookup by the
of_node of pdev->dev; and because np is used to find the pdev, it should
work for the same cases where of_nvmem_cell_get(np) will work.
I'm fine with either, maybe the fallback to of_nvmem_cell_get()
is clearer.
-michael
next prev parent reply other threads:[~2021-04-05 21:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 16:46 [PATCH 0/2] of: net: support non-platform devices in of_get_mac_address() Michael Walle
2021-04-05 16:46 ` [PATCH 1/2] of: net: pass the dst buffer to of_get_mac_address() Michael Walle
2021-04-05 19:19 ` kernel test robot
2021-04-05 21:25 ` Andrew Lunn
2021-04-05 16:46 ` [PATCH 2/2] of: net: fix of_get_mac_addr_nvmem() for PCI and DSA nodes Michael Walle
2021-04-05 21:34 ` Andrew Lunn
2021-04-05 21:46 ` Michael Walle [this message]
2021-04-05 22:13 ` Andrew Lunn
2021-04-06 8:59 ` Michael Walle
2021-04-06 12:40 ` Andrew Lunn
2021-04-07 1:13 ` Rob Herring
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=2d6eef78762562bcbb732179b32f0fd9@walle.cc \
--to=michael@walle.cc \
--cc=andrew@lunn.ch \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).