From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Mateusz Polchlopek <mateusz.polchlopek@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Cc: netdev@vger.kernel.org, horms@kernel.org
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v4 00/12] Add support for Rx timestamping for both ice and iavf drivers.
Date: Tue, 16 Apr 2024 16:28:45 -0700 [thread overview]
Message-ID: <525bc12c-ce69-29f5-6fa9-ff7232d63d7e@intel.com> (raw)
In-Reply-To: <20240410121706.6223-1-mateusz.polchlopek@intel.com>
On 4/10/2024 5:16 AM, Mateusz Polchlopek wrote:
> Initially, during VF creation it registers the PTP clock in
> the system and negotiates with PF it's capabilities. In the
> meantime the PF enables the Flexible Descriptor for VF.
> Only this type of descriptor allows to receive Rx timestamps.
>
> Enabling virtual clock would be possible, though it would probably
> perform poorly due to the lack of direct time access.
>
> Enable timestamping should be done using SIOCSHWTSTAMP ioctl,
> e.g.
> hwstamp_ctl -i $VF -r 14
>
> In order to report the timestamps to userspace, the VF extends
> timestamp to 40b.
>
> To support this feature the flexible descriptors and PTP part
> in iavf driver have been introduced.
A majority of these patches are adding new kernel-doc issues (-Wall).
Could you clean up the ones that are being added by these patches?
Thanks,
Tony
prev parent reply other threads:[~2024-04-16 23:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 12:16 [Intel-wired-lan] [PATCH iwl-next v4 00/12] Add support for Rx timestamping for both ice and iavf drivers Mateusz Polchlopek
2024-04-10 12:16 ` [Intel-wired-lan] [PATCH iwl-next v4 01/12] virtchnl: add support for enabling PTP on iAVF Mateusz Polchlopek
2024-04-10 12:16 ` [Intel-wired-lan] [PATCH iwl-next v4 02/12] ice: support Rx timestamp on flex descriptor Mateusz Polchlopek
2024-04-10 12:16 ` [Intel-wired-lan] [PATCH iwl-next v4 03/12] virtchnl: add enumeration for the rxdid format Mateusz Polchlopek
2024-04-10 12:16 ` [Intel-wired-lan] [PATCH iwl-next v4 04/12] iavf: add support for negotiating flexible RXDID format Mateusz Polchlopek
2024-04-10 12:16 ` [Intel-wired-lan] [PATCH iwl-next v4 05/12] iavf: negotiate PTP capabilities Mateusz Polchlopek
2024-04-10 12:17 ` [Intel-wired-lan] [PATCH iwl-next v4 06/12] iavf: add initial framework for registering PTP clock Mateusz Polchlopek
2024-04-10 12:17 ` [Intel-wired-lan] [PATCH iwl-next v4 07/12] iavf: add support for indirect access to PHC time Mateusz Polchlopek
2024-04-10 12:17 ` [Intel-wired-lan] [PATCH iwl-next v4 08/12] iavf: periodically cache " Mateusz Polchlopek
2024-04-10 12:17 ` [Intel-wired-lan] [PATCH iwl-next v4 09/12] iavf: refactor iavf_clean_rx_irq to support legacy and flex descriptors Mateusz Polchlopek
2024-04-10 12:17 ` [Intel-wired-lan] [PATCH iwl-next v4 10/12] iavf: Implement checking DD desc field Mateusz Polchlopek
2024-04-10 12:17 ` [Intel-wired-lan] [PATCH iwl-next v4 11/12] iavf: handle SIOCSHWTSTAMP and SIOCGHWTSTAMP Mateusz Polchlopek
2024-04-10 12:17 ` [Intel-wired-lan] [PATCH iwl-next v4 12/12] iavf: add support for Rx timestamps to hotpath Mateusz Polchlopek
2024-04-16 23:28 ` Tony Nguyen [this message]
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=525bc12c-ce69-29f5-6fa9-ff7232d63d7e@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=mateusz.polchlopek@intel.com \
--cc=netdev@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).