We try to keep the data path protocol between the switch and the host
API compatible, and identifiable by /sys/class/net/<conduit>/dsa/tagging.
I would argue that the protocol where PTP timestamps are in registers,
vs where they are in PTP header reserved fields, vs where they are
appended as trailers, are 3 different protocols and should not be
presented as "edsa".
For context: I added ArrTSMode support because even with the PTP worker process priority bumped, ptp4l frequently missed RX timestamps.
I can add these as non-default tagging variants that can be selected by the user. "edsa-arrts-trailer" and "edsa-arrts-ptp-reserved”?
Luke