[Intel-wired-lan] [PATCH iwl-next v12 01/14] virtchnl: add support for enabling PTP on iAVF

[Romanowski, Rafal]

> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces at osuosl.org> On Behalf Of
> Mateusz Polchlopek
> Sent: Tuesday, October 22, 2024 1:41 PM
> To: intel-wired-lan at lists.osuosl.org
> Cc: netdev at vger.kernel.org; Keller, Jacob E <jacob.e.keller at intel.com>; Drewek,
> Wojciech <wojciech.drewek at intel.com>; Rahul Rameshbabu
> <rrameshbabu at nvidia.com>; Simon Horman <horms at kernel.org>; Lobakin,
> Aleksander <aleksander.lobakin at intel.com>; Polchlopek, Mateusz
> <mateusz.polchlopek at intel.com>
> Subject: [Intel-wired-lan] [PATCH iwl-next v12 01/14] virtchnl: add support for
> enabling PTP on iAVF
> 
> From: Jacob Keller <jacob.e.keller at intel.com>
> 
> Add support for allowing a VF to enable PTP feature - Rx timestamps
> 
> The new capability is gated by VIRTCHNL_VF_CAP_PTP, which must be set by the
> VF to request access to the new operations. In addition, the
> VIRTCHNL_OP_1588_PTP_CAPS command is used to determine the specific
> capabilities available to the VF.
> 
> This support includes the following additional capabilities:
> 
> * Rx timestamps enabled in the Rx queues (when using flexible advanced
>   descriptors)
> * Read access to PHC time over virtchnl using
>   VIRTCHNL_OP_1588_PTP_GET_TIME
> 
> Extra space is reserved in most structures to allow for future extension (like set
> clock, Tx timestamps).  Additional opcode numbers are reserved and space in the
> virtchnl_ptp_caps structure is specifically set aside for this.
> Additionally, each structure has some space reserved for future extensions to
> allow some flexibility.
> 
> Signed-off-by: Jacob Keller <jacob.e.keller at intel.com>
> Reviewed-by: Wojciech Drewek <wojciech.drewek at intel.com>
> Reviewed-by: Rahul Rameshbabu <rrameshbabu at nvidia.com>
> Reviewed-by: Simon Horman <horms at kernel.org>
> Reviewed-by: Alexander Lobakin <aleksander.lobakin at intel.com>
> Signed-off-by: Mateusz Polchlopek <mateusz.polchlopek at intel.com>

Tested-by: Rafal Romanowski <rafal.romanowski at intel.com>