netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: David Miller <davem@davemloft.net>, mike.looijmans@topic.nl
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, andrew@lunn.ch, robh+dt@kernel.org,
	frowand.list@gmail.com
Subject: Re: [PATCH v2] of_net: Implement of_get_nvmem_mac_address helper
Date: Mon, 26 Mar 2018 10:05:08 -0700	[thread overview]
Message-ID: <40e5302c-0c00-dba0-58d3-77407aa6bde8@gmail.com> (raw)
In-Reply-To: <20180326.125816.1498152294570222508.davem@davemloft.net>

On 03/26/2018 09:58 AM, David Miller wrote:
> From: Mike Looijmans <mike.looijmans@topic.nl>
> Date: Mon, 26 Mar 2018 08:41:29 +0200
> 
>> It's common practice to store MAC addresses for network interfaces into
>> nvmem devices. However the code to actually do this in the kernel lacks,
>> so this patch adds of_get_nvmem_mac_address() for drivers to obtain the
>> address from an nvmem cell provider.
>>
>> This is particulary useful on devices where the ethernet interface cannot
>> be configured by the bootloader, for example because it's in an FPGA.
>>
>> Tested by adapting the cadence macb driver to call this instead of
>> of_get_mac_address().
>>
>> Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
>> ---
>> v2: Use of_nvmem_cell_get to avoid needing the assiciated device
>>     Use void* instead of char*
>>     Add devicetree binding doc
> 
> Like Andrew, I think you should add a new interface for getting the MAC
> address from nvmem.
> 
> And drivers can call both of them if they want OF device tree and
> NVMEM probing for MAC addresses.
> 
> Later you can add a consolidated interface, if necessary, which does
> both and also take a reference to the MAC address buffer of the driver
> in order to deal with the resource allocation issues.

Agreed, also, how does this fit with Alban's patch series here:

https://lkml.org/lkml/2018/3/24/312

do you depend on those changes at all?
-- 
Florian

  reply	other threads:[~2018-03-26 17:05 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-23 14:24 [PATCH] of_net: Implement of_get_nvmem_mac_address helper Mike Looijmans
2018-03-23 15:11 ` Andrew Lunn
2018-03-23 19:20   ` Mike Looijmans
2018-03-23 19:33     ` Florian Fainelli
2018-03-24 16:17       ` Mike Looijmans
2018-03-24 18:53         ` Andrew Lunn
2018-03-25  8:17           ` Mike Looijmans
2018-03-25 21:04             ` Andrew Lunn
2018-03-26  6:54             ` Mike Looijmans
2018-03-23 19:42     ` Andrew Lunn
2018-03-24 16:03       ` Mike Looijmans
2018-03-26  6:41   ` [PATCH v2] " Mike Looijmans
2018-03-26 15:50     ` Andrew Lunn
2018-03-26 18:25       ` Mike Looijmans
2018-03-26 18:41         ` Andrew Lunn
2018-03-26 16:58     ` David Miller
2018-03-26 17:05       ` Florian Fainelli [this message]
2018-03-26 18:21         ` Mike Looijmans
2018-03-27  9:52     ` [PATCH v3 0/2] " Mike Looijmans
2018-03-27  9:52       ` [PATCH v3 1/2] " Mike Looijmans
2018-03-27 22:50         ` Florian Fainelli
2018-03-29  5:31           ` Mike Looijmans
2018-03-27  9:52       ` [PATCH v3 2/2] net: macb: Try to retrieve MAC addess from nvmem provider Mike Looijmans
2018-03-28  8:00         ` Nicolas Ferre
2018-03-27 22:43       ` [PATCH v3 0/2] of_net: Implement of_get_nvmem_mac_address helper Andrew Lunn
2018-03-29  5:29       ` [PATCH v4 " Mike Looijmans
2018-03-29  5:29         ` [PATCH v4 1/2] " Mike Looijmans
2018-03-29  5:29         ` [PATCH v4 2/2] net: macb: Try to retrieve MAC addess from nvmem provider Mike Looijmans
2018-03-30 14:40         ` [PATCH v4 0/2] of_net: Implement of_get_nvmem_mac_address helper David Miller
2018-03-31 17:20           ` Mike Looijmans
2018-03-31 17:27             ` Andrew Lunn

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=40e5302c-0c00-dba0-58d3-77407aa6bde8@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=frowand.list@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.looijmans@topic.nl \
    --cc=netdev@vger.kernel.org \
    --cc=robh+dt@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).