summaryrefslogtreecommitdiff
path: root/tools/lib/python
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2026-10-16 18:04:13 -0700
committerJakub Kicinski <kuba@kernel.org>2026-10-16 18:04:14 -0700
commit23e687079e89a4552272636c48af96872bb7061b (patch)
tree5798f124678ec5a20ca596b9b478b874c47b0fe3 /tools/lib/python
parent00accbd9d5021b942a16078bd5717d7865f6971c (diff)
parentd347ab5cf809365e7b3749dc91d77e89e4b7ec3f (diff)
Merge branch 'net-freescale-fix-ptp_extts_request2-for-qoriq-1588'
Vincent Jardin via says: ==================== net: freescale: fix PTP_EXTTS_REQUEST2 for QorIQ 1588 Since commit 7c571ac57d9d ("net: ptp: introduce .supported_extts_flags to ptp_clock_info"), the PTP core rejects every PTP_EXTTS_REQUEST2 request for a driver that does not set .supported_extts_flags. The three users of the QorIQ 1588 timer (dpaa2-ptp, enetc, ptp_qoriq) do not set it, so linuxptp ts2phc cannot arm their external timestamp inputs. The timer timestamps the rising edge only, since ptp_qoriq_init() clears ETEP1 and ETEP2. Each patch declares PTP_RISING_EDGE | PTP_STRICT_FLAGS for one driver. With PTP_STRICT_FLAGS declared, the core checks the edge flags of the legacy PTP_EXTTS_REQUEST ioctl too: a legacy request for the falling edge, or for both edges, now fails with -EOPNOTSUPP instead of being timestamped on the rising edge. Each commit message says so. Patch 1 fixes the failure seen on an LX2160A board. Patches 2 and 3 are build-tested/code review only. ==================== Link: https://patch.msgid.link/20261009-for-upstream-qoriq-ptp-extts-flags-v2-0-0f4eeff2295d@free.fr Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/lib/python')
0 files changed, 0 insertions, 0 deletions