[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251027095139.399855-1-paul.sage@42.fr>
Date: Mon, 27 Oct 2025 10:51:39 +0100
From: Paul SAGE <paul.sage@...fr>
To: andrew@...n.ch
Cc: andrew+netdev@...n.ch,
davem@...emloft.net,
edumazet@...gle.com,
kuba@...nel.org,
linux-kernel@...r.kernel.org,
mchan@...adcom.com,
netdev@...r.kernel.org,
pabeni@...hat.com,
paul.sage@...fr,
pavan.chebbi@...adcom.com,
vinc@...fr
Subject: RE: Andrew Lunn
The tg3 currently call eth_platform_get_mac_address to retrieve the
MAC address from the device tree before trying the mailbox,
NVRAM and MAC registers.
However, this function only retrieves the MAC address from the device
tree using of_get_mac_address.
We are using device_get_mac_address, which use fwnode to obtain a MAC
address using the ACPI, so as we understand fwnode is an
abstraction layer for both the device tree (on ARM) and ACPI (on x86)
If true, it could be appropriate to replace the call to replace
eth_platform_get_mac_address with device_get_mac_address. This would
avoid running the entire function only to later check for a dummy
address.
Do you see any regression possible with this change ?
Powered by blists - more mailing lists