[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MN2PR11MB466441745C8C1D64835C51739B5C2@MN2PR11MB4664.namprd11.prod.outlook.com>
Date: Thu, 7 Nov 2024 09:01:41 +0000
From: "Kubalewski, Arkadiusz" <arkadiusz.kubalewski@...el.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
"Nguyen, Anthony L" <anthony.l.nguyen@...el.com>, "Kitszel, Przemyslaw"
<przemyslaw.kitszel@...el.com>, "davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com" <edumazet@...gle.com>, "pabeni@...hat.com"
<pabeni@...hat.com>, "richardcochran@...il.com" <richardcochran@...il.com>,
"Loktionov, Aleksandr" <aleksandr.loktionov@...el.com>
Subject: RE: [PATCH net-next v3 1/2] ptp: add control over HW timestamp latch
point
>From: Jakub Kicinski <kuba@...nel.org>
>Sent: Wednesday, November 6, 2024 3:05 AM
>
>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.
Ok, thank you for feedback.
Richard do you agree with Kuba?
Thank you!
Arkadiusz
Powered by blists - more mailing lists