This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM4378: DP83826 Eth PHY Linux driver for TI AM4378 on kernel 4.19.94 version

Part Number: AM4378
Other Parts Discussed in Thread: DP83TC811, DP83826I

Target SOC : AM4378(custom board)

 Linux  version : 4.19.94 

TI SDK version : 06.03.00.106

We are using TI DP83826 PHY, we observed that any TI phy driver(dp83822.c) is not attached, appearing as "unknown, so PHY driver is identified as "Generic PHY." instead of TI phy even though we enabled phy drivers in kernel.

kernel configuration for TI phy support:

CONFIG_DP83822_PHY=y

# CONFIG_DP83TC811_PHY is not set

CONFIG_DP83848_PHY=y

CONFIG_DP83867_PHY=y

here is the driver probe output log:

root@picv6-1:~# dmesg | grep phy

Booting Linux on physical CPU 0x0

libphy: Fixed MDIO Bus: probed

davinci_mdio 4a101000.mdio: detected phy mask fffffffe

libphy: 4a101000.mdio: probed

davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver unknown

cpsw 4a100000.ethernet: No slave[0] phy_id, phy-handle, or fixed-link property

libphy: PHY  not found

net eth0: phy "" not found on slave 0, err -19

Generic PHY 4a101000.mdio:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=4a101000.mdio:00, irq=POLL)

We had Microchip LAN8740 PHY on same hardware,  LAN8740 driver is correctly detected.

Logs:

root@picv6-1:~# dmesg | grep phy

Booting Linux on physical CPU 0x0

libphy: Fixed MDIO Bus: probed

davinci_mdio 4a101000.mdio: detected phy mask fffffffe

libphy: 4a101000.mdio: probed

davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8740

cpsw 4a100000.ethernet: No slave[0] phy_id, phy-handle, or fixed-link property

libphy: PHY  not found

net eth0: phy "" not found on slave 0, err -19

SMSC LAN8740 4a101000.mdio:00: attached PHY driver [SMSC LAN8740] (mii_bus:phy_addr=4a101000.mdio:00, irq=POLL)

We kindly request your assistance in investigating why the TI DP83826 PHY drivers are not being detected correctly. Also please provide if you have updated/specific drivers for TI DP83826I that we need to use.