summaryrefslogtreecommitdiff
path: root/firmware
diff options
context:
space:
mode:
authorAhmad Fatoum <a.fatoum@pengutronix.de>2022-11-30 12:51:57 +0100
committerSascha Hauer <s.hauer@pengutronix.de>2022-12-02 09:56:02 +0100
commit84c9f28a2806a1072b8a57bc38e35605db6eb916 (patch)
tree13cc1af6427391dcc9b85c748e29ede816bcf0b9 /firmware
parent26332d8866c7d1db1d9789da1b6554a04735ed29 (diff)
downloadbarebox-84c9f28a2806a1072b8a57bc38e35605db6eb916.tar.gz
net: bcmgenet: fix OF node of MII bus controller
The bcmgenet device tree binding describes the MDIO controller as a subnode of the Ethernet controller node. Linux handles this by having a driver for each of the MAC and MDIO controller, but in barebox we keep a single driver and largely ignore the subnode. Since Commit 8abc2059298d ("net: add support for MDIO devices"), this leads to following error message: ERROR: miibus0: /scb/ethernet@7d580000/mdio@e14 PHY address 3604 is too large Give the MII bus the correct device tree node to fix this. We already do it this way in the designware_eqos driver. This was tested on a Raspberry Pi 4b, where Link up and reading PHY ID of 600d 84a2 is sensible (matches PHY_ID_BCM54210E). DHCP though didn't work for me with or without this patch. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de> Link: https://lore.barebox.org/20221130115157.3858878-1-a.fatoum@pengutronix.de Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Diffstat (limited to 'firmware')
0 files changed, 0 insertions, 0 deletions