[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <VI1PR0402MB3600DCD22084A6A0D5190859FF0F0@VI1PR0402MB3600.eurprd04.prod.outlook.com>
Date: Mon, 13 May 2019 03:31:59 +0000
From: Andy Duan <fugang.duan@....com>
To: Andrew Lunn <andrew@...n.ch>
CC: "davem@...emloft.net" <davem@...emloft.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"ynezz@...e.cz" <ynezz@...e.cz>,
"john@...ozen.org" <john@...ozen.org>,
"bgolaszewski@...libre.com" <bgolaszewski@...libre.com>,
Petr Štetiar <ynezz@...e.cz>,
Maxime Ripard <maxime.ripard@...tlin.com>
Subject: RE: [EXT] Re: [PATCH net 2/3] of_net: add property
"nvmem-mac-address" for of_get_mac_addr()
From: Andrew Lunn <andrew@...n.ch> Sent: Saturday, May 11, 2019 2:18 AM
> On Fri, May 10, 2019 at 08:24:03AM +0000, Andy Duan wrote:
> > If MAC address read from nvmem cell and it is valid mac address,
> > .of_get_mac_addr_nvmem() add new property "nvmem-mac-address" in
> > ethernet node. Once user call .of_get_mac_address() to get MAC address
> > again, it can read valid MAC address from device tree in directly.
>
> I suspect putting the MAC address into OF will go away in a follow up patch. It
> is a bad idea.
>
> Andrew
I don't know the history why does of_get_mac_addr_nvmem() add the new property
"nvmem-mac-address" into OF. But if it already did that, so the patch add the property
check in . of_get_mac_address() to avoid multiple read nvmem cells in driver.
Andy
Powered by blists - more mailing lists