On Sat, Sep 28, 2024 at 02:05:13PM -0700, Drew Fustini wrote: > On Fri, Sep 27, 2024 at 01:58:40PM +0200, Andrew Lunn wrote: > > > I tried to setup an nfs server with a rootfs on my local network. I can > > > mount it okay from my laptop so I think it is working okay. However, it > > > does not seem to work on the lpi4a [3]. It appears the rgmii-id > > > validation fails and the dwmac driver can not open the phy: > > > > > > thead-dwmac ffe7060000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0 > > > thead-dwmac ffe7060000.ethernet eth0: validation of rgmii-id with support \ > > > 00,00000000,00000000,00006280 and advertisementa \ > > > 00,00000000,00000000,00006280 failed: -EINVAL > > > thead-dwmac ffe7060000.ethernet eth0: __stmmac_open: Cannot attach to PHY (error: -22) > > > > Given what Emil said, i would suggest flipping the MDIO busses > > around. Put the PHYs on gmac1's MDIO bus, and set the pinmux so that > > its MDIO bus controller is connected to the outside world. Then, when > > gmac1 probes first, its MDIO bus will be probed at the same time, and > > its PHY found. > > > > Andrew > > I'm trying to configure the pinmux to have gmac1 control the mdio bus > but it seems I've not done so correctly. I changed pins "GMAC0_MDC" and > "GMAC0_MDIO" to function "gmac1" (see the patch below). > > I don't see any errors about the dwmac or phy in the boot log [1] but > ultimately there is no carrier detected and the ethernet interface does > not come up. > > Section "3.3.4.103 G3_MUXCFG_007" in the TH1520 System User Manual shows > that bits [19:16] control GMAC0_MDIO_MUX_CFG where value of 2 selects > GMAC1_MDIO. Similarly, bits [15:12] control GMAC0_MDC_MUX_CFG where a > value of 2 also selects GMAC1_MDC. > > Emil - do you have any suggestion as to what I might be doing wrong with > the pinmux? I've been thinking about this and I don't think there is any problem on the LPi4a. Both Ethernet jacks work when I have the mdio bus muxed for gmac0 to control it. It seems to control both phy's okay. Earlier, I tried to setup nfs root but it didn't work. I believe this is just due to my ignorance of how to configure it correctly. I've instead switched to just adding 'ip=dhcp' to the kernel command. This causes stmmac_open() to happen shortly after the thead-dwmac is probed for both gmac0 and gmac1. The phy is found for both and there are no errors. Without 'ip=dhcp', stmmac_open() is not called until around 40 seconds into boot when NetworkManager tries to open it. Everything works correctly but the delay of over 30 seconds from thead-dwmac probe to interface up looks odd in the logs, but I am pretty sure this is just due the point in time at which NetworkManager decides to bring up the network interfaces. Booting with gmac0 connected to Ethernet cable: https://gist.github.com/pdp7/e1a8e7666706c7d3c99b6b7a3b43f070 Booting with gmac1 connected to Ethernet cable: https://gist.github.com/pdp7/8a9c2066a2c20377ec3b479213b9be4c thead-dwmac probe for gmac happens around 6 seconds. stmmac_open() occurs shortly after that. The interface is up by around 10 seconds into boot. DHCP request works okay and the interface is up and working once the shell is ready. In short, I believe the dts configuration in patch 3/3 of this series works okay for both Ethernet ports on the LPi4a. Thanks, Drew
