From: Jakub Kicinski <kuba@kernel.org>
To: Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
intel-wired-lan@lists.osuosl.org, anthony.l.nguyen@intel.com,
przemyslaw.kitszel@intel.com, davem@davemloft.net,
edumazet@google.com, pabeni@redhat.com, richardcochran@gmail.com,
Aleksandr Loktionov <aleksandr.loktionov@intel.com>
Subject: Re: [PATCH net-next v3 1/2] ptp: add control over HW timestamp latch point
Date: Tue, 5 Nov 2024 18:04:57 -0800 [thread overview]
Message-ID: <20241105180457.01c54f15@kernel.org> (raw)
In-Reply-To: <20241106010756.1588973-2-arkadiusz.kubalewski@intel.com>
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@intel.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.
next prev parent reply other threads:[~2024-11-06 2:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 1:07 [PATCH net-next v3 0/2] ptp: add control over HW timestamp latch point Arkadiusz Kubalewski
2024-11-06 1:07 ` [PATCH net-next v3 1/2] " Arkadiusz Kubalewski
2024-11-06 2:04 ` Jakub Kicinski [this message]
2024-11-07 9:01 ` Kubalewski, Arkadiusz
2024-11-07 17:54 ` Richard Cochran
2024-11-06 17:45 ` Andrew Lunn
2024-11-07 9:14 ` [Intel-wired-lan] " Kubalewski, Arkadiusz
2024-11-06 1:07 ` [PATCH net-next v3 2/2] ice: " Arkadiusz Kubalewski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241105180457.01c54f15@kernel.org \
--to=kuba@kernel.org \
--cc=aleksandr.loktionov@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=richardcochran@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).