topic Re: NXP2160a use ptp Hardware Timestamping print. "PTP Hardware Clock: none" in QorIQ

NXP2160a use ptp Hardware Timestamping print. "PTP Hardware Clock: none"

chunky — Wed, 18 Aug 2021 08:56:31 GMT

I configed the kernel (from lsdk) as following :

# PTP clock support

CONFIG_PTP_1588_CLOCK=y #PTP clock support

CONFIG_PTP_1588_CLOCK_DTE=y #Broadcom DTE as PTP clock

CONFIG_PTP_1588_CLOCK_QORIQ=y #Freescale QorIQ 1588 timer as PTP clock

CONFIG_NETWORK_PHY_TIMESTAMPING=y #Timestamping in PHY devices

CONFIG_MACB_USE_HWSTAMP=y #Use IEEE 1588 hwstamp

CONFIG_NET_VENDOR_FREESCALE=y #Freescale devices

CONFIG_PPS=y #PPS support ,Acordding to ptp4l sdk required--chenhy

CONFIG_NET_PTP_CLASSIFY=y

CONFIG_GIANFAR=y #under all from LSDKUG_Rev20.12

CONFIG_FSL_SDK_DPAA_ETH=y

CONFIG_FSL_DPAA_TS=y

CONFIG_FSL_DPAA_ETH=y

CONFIG_FSL_DPAA2_ETH=y

CONFIG_FSL_DPAA2_PTP_CLOCK=y

CONFIG_FSL_ENETC=y

CONFIG_FSL_ENETC_PTP_CLOCK=y

CONFIG_NET_DSA_MSCC_FELIX=y

CONFIG_PTP_1588_CLOCK_DPAA=y

CONFIG_FSL_ENETC_HW_TIMESTAMPING=y

CONFIG_FSL_MC_BUS=y #for fsl-mc@80c000000

CONFIG_FSL_MC_UAPI_SUPPORT=y #for fsl-mc@80c000000

CONFIG_FSL_MC_ENET=y

CONFIG_TARGET_LX2160ARDB=y #obj-$(CONFIG_TARGET_LX2160ARDB) += eth_lx2160ardb.o

CONFIG_TARGET_LX2160AQDS=y #obj-$(CONFIG_TARGET_LX2160AQDS) += eth_lx2160aqds.o

CONFIG_FSL_XGMAC_MDIO=y #for obj-$(CONFIG_FSL_XGMAC_MDIO) += xgmac_mdio.o

CONFIG_PCI_MSI=y

CONFIG_FSL_DPAA_1588=y

# end of PTP clock support

but when the 2160 running. I input. ""ethtool -T eth1",the result is:

Why display “ "PTP Hardware Clock: none"”？

Please help me，thanks！

Re: NXP2160a use ptp Hardware Timestamping print. "PTP Hardware Clock: none"

yipingwang — Thu, 19 Aug 2021 07:10:59 GMT

I built Kernel Image with the default Kernel configuration file provided in LSDK 20.12(please refer to the attachment), and verified it on LX2160ARDB, I used DPL dpl-eth.19.dtb on the target board, get the result as the following.

root@localhost:~# ethtool -T eth0
Time stamping parameters for eth0:
Capabilities:
hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE)
hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE)
hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE)
PTP Hardware Clock: 0
Hardware Transmit Timestamp Modes:
off (HWTSTAMP_TX_OFF)
on (HWTSTAMP_TX_ON)
one-step-sync (HWTSTAMP_TX_ONESTEP_SYNC)
Hardware Receive Filter Modes:
none (HWTSTAMP_FILTER_NONE)
all (HWTSTAMP_FILTER_ALL)
root@localhost:~# ethtool -T eth1
Time stamping parameters for eth1:
Capabilities:
hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE)
hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE)
hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE)
PTP Hardware Clock: 0
Hardware Transmit Timestamp Modes:
off (HWTSTAMP_TX_OFF)
on (HWTSTAMP_TX_ON)
one-step-sync (HWTSTAMP_TX_ONESTEP_SYNC)
Hardware Receive Filter Modes:
none (HWTSTAMP_FILTER_NONE)
all (HWTSTAMP_FILTER_ALL)
root@localhost:~# ls-listni
dprc.1/dpni.1 (interface: eth0, end point: dpmac.2)
dprc.1/dpni.0 (interface: eth1, end point: dpmac.17)

Please check dts configuration:

ptp-timer@8b95000 {
compatible = "fsl,dpaa2-ptp";
reg = <0x0 0x8b95000 0x0 0x100>;
clocks = <&clockgen 4 1>;
little-endian;
fsl,extts-fifo;
};

Re: NXP2160a use ptp Hardware Timestamping print. "PTP Hardware Clock: none"

chunky — Thu, 19 Aug 2021 08:40:04 GMT

I find a same problem as mine,the address is :

https://community.nxp.com/t5/Layerscape/Failed-to-get-PTP-Hardware-Clock-support-on-LA1224ARDB/m-p/1151884#M6634

He solved the problem by update DPL file to support PTP,

Maybe my DPL file have some problem,I want to know How to modify DPL file to support PTP?

On the other hand ,Can you show me your DPL file?

For 2160 ,is the DPL file named “flexbuild_lsdk/packages/firmware/mc_utils/config/lx2160a/RDB/dpl-eth.19.dts” ?

Re: NXP2160a use ptp Hardware Timestamping print. "PTP Hardware Clock: none"

yipingwang — Fri, 20 Aug 2021 02:36:50 GMT

Do you use LSDK 20.12?

I just use DPL file from LSDK 20.12, please refer to the attachment.

Please make sure that you have the following patch applied in your DPL file.

https://source.codeaurora.org/external/qoriq/qoriq-components/mc-utils/commit/config/lx2160a/RDB?h=LSDK-20.12&id=6aca560c630dc54afdef382c506f214b28f4985e

Re: NXP2160a use ptp Hardware Timestamping print. "PTP Hardware Clock: none"

chunky — Fri, 20 Aug 2021 08:24:05 GMT

Thanks.

Good news is the NXP2160's PTP function goes normal after I modify DPL file dpl-eth.19.dts depend on the following address:

https://source.codeaurora.org/external/qoriq/qoriq-components/mc-utils/commit/config/lx2160a/RDB?h=LSDK-20.12&id=6aca560c630dc54afdef382c506f214b28f4985e

But when I modify DPL file dpl-eth.19.dts,the display is:

root@****:~# ethtool -T eth1

Time stamping parameters for eth1:

Capabilities:

hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE)

hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE)

hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE)

PTP Hardware Clock: 0

Hardware Transmit Timestamp Modes:

off (HWTSTAMP_TX_OFF)

on (HWTSTAMP_TX_ON)

Hardware Receive Filter Modes:

none (HWTSTAMP_FILTER_NONE)

all (HWTSTAMP_FILTER_ALL)

# ls /dev/ptp0

/dev/ptp0

# ls /dev/pps0

/dev/pps0

# ./ptp4l -i eth0 -m

ptp4l[391.041]: selected /dev/ptp0 as PTP clock

ptp4l[391.081]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE

ptp4l[391.081]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE

ptp4l[397.808]: port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES

ptp4l[397.808]: selected local clock 1aa1f5.fffe.d0a3d7 as best master

ptp4l[397.808]: port 1: assuming the grand master role

# ./ptp4l -i eth0 -m -s

ptp4l[452.868]: selected /dev/ptp0 as PTP clock

ptp4l[452.908]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE

ptp4l[452.909]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE

ptp4l[460.369]: selected local clock 1aa1f5.fffe.d0a3d7 as best master

ptp4l[468.206]: selected local clock 1aa1f5.fffe.d0a3d7 as best master

ptp4l[475.953]: selected local clock 1aa1f5.fffe.d0a3d7 as best master

ptp4l[482.426]: selected local clock 1aa1f5.fffe.d0a3d7 as best master

l# ethtool -T eth0

Time stamping parameters for eth0:

Capabilities:

hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE)

hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE)

hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE)

PTP Hardware Clock: 0

Hardware Transmit Timestamp Modes:

off (HWTSTAMP_TX_OFF)

on (HWTSTAMP_TX_ON)

Hardware Receive Filter Modes:

none (HWTSTAMP_FILTER_NONE)

all (HWTSTAMP_FILTER_ALL)

# ethtool -T eth2

Time stamping parameters for eth2:

Capabilities:

hardware-transmit (SOF_TIMESTAMPING_TX_HARDWARE)

hardware-receive (SOF_TIMESTAMPING_RX_HARDWARE)

hardware-raw-clock (SOF_TIMESTAMPING_RAW_HARDWARE)

PTP Hardware Clock: 0

Hardware Transmit Timestamp Modes:

off (HWTSTAMP_TX_OFF)

on (HWTSTAMP_TX_ON)

Hardware Receive Filter Modes:

none (HWTSTAMP_FILTER_NONE)

all (HWTSTAMP_FILTER_ALL)

# restool dprc show dprc.1 | grep dprtc

dprtc.0 plugged

# ls-listni

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

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

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

dprc.1/dpni.7 (interface: eth3, end point: dpmac.7)

dprc.1/dpni.6 (interface: eth4, end point: dpmac.4)

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

dprc.1/dpni.4 (interface: eth6, end point: dpmac.10)

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

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

dprc.1/dpni.1 (interface: eth9, end point: dpmac.14)

dprc.1/dpni.0 (interface: eth10, end point: dpmac.11)

Now my question is why eth0 to eth10 :ethtool -T eth0~10 all display “PTP Hardware Clock: 0”,how to config each eth* has its own clock?

Just like :for eth1 is “PTP Hardware Clock: 1”, for eth2 is “PTP Hardware Clock: 2”,………for eth10 is “PTP Hardware Clock: 10”.

Thank you for your help!

Re: NXP2160a use ptp Hardware Timestamping print. "PTP Hardware Clock: none"

yipingwang — Wed, 25 Aug 2021 06:15:41 GMT

There is only one 1588 module common for all the interfaces in the system that is why they see only one PTP hardware clock.

Check the DPAA2 reference manual: "The 1588 timer module interfaces to up to an unlimited number of 10/100/1000 or 10G Ethernet MACs, providing current time, alarm, and fiper support.".