[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241105180457.01c54f15@kernel.org>
Date: Tue, 5 Nov 2024 18:04:57 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
intel-wired-lan@...ts.osuosl.org, anthony.l.nguyen@...el.com,
przemyslaw.kitszel@...el.com, davem@...emloft.net, edumazet@...gle.com,
pabeni@...hat.com, richardcochran@...il.com, Aleksandr Loktionov
<aleksandr.loktionov@...el.com>
Subject: Re: [PATCH net-next v3 1/2] ptp: add control over HW timestamp
latch point
On Wed, 6 Nov 2024 02:07:55 +0100 Arkadiusz Kubalewski wrote:
> +What: /sys/class/ptp/ptp<N>/ts_point
> +Date: October 2024
> +Contact: Arkadiusz Kubalewski <arkadiusz.kubalewski@...el.com>
> +Description:
> + This file provides control over the point in time in
> + which the HW timestamp is latched. As specified in IEEE
> + 802.3cx, the latch point can be either at the beginning
> + or after the end of Start of Frame Delimiter (SFD).
> + Value "1" means the timestamp is latched at the
> + beginning of the SFD. Value "2" means that timestamp is
> + latched after the end of SFD.
Richard has the final say but IMO packet timestamping config does not
belong to the PHC, rather ndo_hwtstamp_set.
Powered by blists - more mailing lists