[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87h6fyfqo9.fsf@nvidia.com>
Date: Thu, 18 Apr 2024 11:49:57 -0700
From: Rahul Rameshbabu <rrameshbabu@...dia.com>
To: Mateusz Polchlopek <mateusz.polchlopek@...el.com>
Cc: intel-wired-lan@...ts.osuosl.org, netdev@...r.kernel.org,
horms@...nel.org, anthony.l.nguyen@...el.com, Jacob Keller
<jacob.e.keller@...el.com>, Wojciech Drewek <wojciech.drewek@...el.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v5 01/12] virtchnl: add
support for enabling PTP on iAVF
On Thu, 18 Apr, 2024 01:24:49 -0400 Mateusz Polchlopek <mateusz.polchlopek@...el.com> wrote:
> From: Jacob Keller <jacob.e.keller@...el.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.
>
> Reviewed-by: Wojciech Drewek <wojciech.drewek@...el.com>
> Signed-off-by: Jacob Keller <jacob.e.keller@...el.com>
> Signed-off-by: Mateusz Polchlopek <mateusz.polchlopek@...el.com>
> ---
Reviewed-by: Rahul Rameshbabu <rrameshbabu@...dia.com>
Powered by blists - more mailing lists