LX2160ARDB mdio access failed after dpdk initialized

[jackho]

Hi,

We want to use mdio read/write phy register after dpdk initialization, but access failed.

Before dpdk initial:

root@lx2160ardbrev2:~# ls-listni

dprc.1/dpni.1 (interface: eth0, end point: dpmac.3)

dprc.1/dpni.0 (interface: eth1, end point: dpmac.6)

root@lx2160ardbrev2:# mdio read eth0 0x3.0x0

phy addr: 0x3

read reg: 0x0 value : 0x2040

After dpdk initialized:

root@lx2160ardbrev2:~# ls-listni

dprc.1/dpni.3 (interface: eth0, end point: dpdmux.0.1)

dprc.1/dpni.0 (interface: eth1, end point: dpmac.6)

dprc.1/dprc.3/dpni.4 (end point: dpni.2)

dprc.1/dprc.2/dpni.2 (end point: dpni.4)

dprc.1/dprc.2/dpni.1 (end point: dpdmux.0.2)

root@lx2160ardbrev2:# mdio read eth0 0x3.0x0

Operation not supported! "main" : line: 100

Could you let us know how to access phy after dpdk initialization?

BR,

Jack 

[jackho]

Hi @yipingwang 

Is there any way we can access eth0 phy after DPDK initialization?

How to access eth0 phy register after eth0 connect to dpdmux?

Thanks.

BR,

Jack Ho

[yipingwang]

After DPDK initialization eth0 connects to dpdmux not DPMAC device.

You need to use mdio to read eth1 before and after DPDK initialization.

[yipingwang]

From the log to see, the dpmac had been changed after customer initialized dpdk, so customer need to check which MAC is connected to eth0, and this can be done by running "ls-listmac" command.

In my local environment, it can still access the phy after dpdk is initialized if it does not affect the DPMAC of eth interface, which is related to the parameters.

root@localhost:~# ls-listni

dprc.1/dpni.1 (interface: eth1, end point: dpmac.2)

dprc.1/dpni.0 (interface: eth2, end point: dpmac.17)

dprc.1/dprc.2/dpni.2 (end point: dpmac.5)

root@localhost:~# ./a.out eth2 0x2.0x0 read phy addr: 0x1 reg: 0x2 value : 0xffff