I am using an LS1046A custom board using SDK-1703 version.
I am using AR8035-AL1B 1G phy connected to fm1-mac3 via RGMII interface.
If you link down/up after about 30 minutes after booting, you will see a phenomenon that the up will not work.
It seems that the initialization is not working properly. Is there a solution?
------------------------- test -----------------------------------
10:59:59 up 33 min, 1 user, load average: 0.00, 0.00, 0.00
root@ls1046ardb:~# ifconfig fm1-mac3 down
root@ls1046ardb:~# ifconfig fm1-mac3 up
SIOCSIFFLAGS: No such device
… dmesg …
[ 1992.532681] fsl_dpa fsl,dpaa:ethernet@2 fm1-mac3: Could not connect to PHY /soc/fman@1a00000/mdio@fc000/ethernet-phy@1
[ 1992.532687] fsl_dpa fsl,dpaa:ethernet@2 fm1-mac3: init_phy() = -19
Linux Kernel provided in SDK 2.0 1703 doesn't include AR8035 PHY driver.
Please refer to PHY AR8035 driver patch provided in http://linux-kernel.2935.n7.nabble.com/PATCH-net-phy-Add-Atheros-AR8035-PHY-support-td637283.html
Please enable ATHEROS_PHY in Linux Kernel.
In addition, would you please provide the result of command "mdio list" in u-boot?
Would you please also send your dts file to me to do more investigation.
Thank you for answer.
The point of the question seems to have not been communicated well.
We have connected the AR8035 and are using it well.
If you don't just do the link down command, ethernet works without problems.
However, if you link down and up after about 30 minutes, it does not come back.
This is the result of mdio list.
=> mdio list
0 - AR8035 <--> FM1@DTSEC6
Attach the kernel net folder source code and dts & config files.
Could you please review why the link doesn't come back to life?
In your Kernel source code, I didn't find PHY driver for AR8035, please apply the following patch to your Linux Kernel and enable ATHEROS_PHY in Kernel configuration file.