[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <525bc12c-ce69-29f5-6fa9-ff7232d63d7e@intel.com>
Date: Tue, 16 Apr 2024 16:28:45 -0700
From: Tony Nguyen <anthony.l.nguyen@...el.com>
To: Mateusz Polchlopek <mateusz.polchlopek@...el.com>,
<intel-wired-lan@...ts.osuosl.org>
CC: <netdev@...r.kernel.org>, <horms@...nel.org>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v4 00/12] Add support for Rx
timestamping for both ice and iavf drivers.
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
Powered by blists - more mailing lists