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

2024-06-08 Thread Simon Horman
On Tue, Jun 04, 2024 at 09:13:49AM -0400, Mateusz Polchlopek wrote: > From: Jacob Keller > > 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 addit

Re: [Intel-wired-lan] [PATCH iwl-next v7 04/12] iavf: add support for negotiating flexible RXDID format

2024-06-08 Thread Simon Horman
On Tue, Jun 04, 2024 at 09:13:52AM -0400, Mateusz Polchlopek wrote: > From: Jacob Keller > > Enable support for VIRTCHNL_VF_OFFLOAD_RX_FLEX_DESC, to enable the VF > driver the ability to determine what Rx descriptor formats are > available. This requires sending an additional message during > ini

Re: [Intel-wired-lan] [PATCH iwl-next v7 02/12] ice: support Rx timestamp on flex descriptor

2024-06-08 Thread Simon Horman
On Tue, Jun 04, 2024 at 09:13:50AM -0400, Mateusz Polchlopek wrote: > From: Simei Su > > To support Rx timestamp offload, VIRTCHNL_OP_1588_PTP_CAPS is sent by > the VF to request PTP capability and responded by the PF what capability > is enabled for that VF. > > Hardware captures timestamps whi

Re: [Intel-wired-lan] [PATCH iwl-next v7 03/12] virtchnl: add enumeration for the rxdid format

2024-06-08 Thread Simon Horman
On Tue, Jun 04, 2024 at 09:13:51AM -0400, Mateusz Polchlopek wrote: > From: Jacob Keller > > Support for allowing VF to negotiate the descriptor format requires that > the VF specify which descriptor format to use when requesting Rx queues. > The VF is supposed to request the set of supported for

Re: [Intel-wired-lan] [PATCH iwl-next v7 04/12] iavf: add support for negotiating flexible RXDID format

2024-06-08 Thread Simon Horman
On Tue, Jun 04, 2024 at 09:13:52AM -0400, Mateusz Polchlopek wrote: > From: Jacob Keller > > Enable support for VIRTCHNL_VF_OFFLOAD_RX_FLEX_DESC, to enable the VF > driver the ability to determine what Rx descriptor formats are > available. This requires sending an additional message during > ini

Re: [Intel-wired-lan] [PATCH iwl-next v7 05/12] iavf: negotiate PTP capabilities

2024-06-08 Thread Simon Horman
On Tue, Jun 04, 2024 at 09:13:53AM -0400, Mateusz Polchlopek wrote: > From: Jacob Keller > > Add a new extended capabilities negotiation to exchange information from > the PF about what PTP capabilities are supported by this VF. This > requires sending a VIRTCHNL_OP_1588_PTP_GET_CAPS message, and

Re: [Intel-wired-lan] [PATCH iwl-next v7 06/12] iavf: add initial framework for registering PTP clock

2024-06-08 Thread Simon Horman
On Tue, Jun 04, 2024 at 09:13:54AM -0400, Mateusz Polchlopek wrote: > From: Jacob Keller > > Add the iavf_ptp.c file and fill it in with a skeleton framework to > allow registering the PTP clock device. > Add implementation of helper functions to check if a PTP capability > is supported and handl

Re: [Intel-wired-lan] [PATCH iwl-next v7 07/12] iavf: add support for indirect access to PHC time

2024-06-08 Thread Simon Horman
On Tue, Jun 04, 2024 at 09:13:55AM -0400, Mateusz Polchlopek wrote: > From: Jacob Keller > > Implement support for reading the PHC time indirectly via the > VIRTCHNL_OP_1588_PTP_GET_TIME operation. > > Based on some simple tests with ftrace, the latency of the indirect > clock access appears to

Re: [Intel-wired-lan] [PATCH iwl-next v7 08/12] iavf: periodically cache PHC time

2024-06-08 Thread Simon Horman
On Tue, Jun 04, 2024 at 09:13:56AM -0400, Mateusz Polchlopek wrote: > From: Jacob Keller > > The Rx timestamps reported by hardware may only have 32 bits of storage > for nanosecond time. These timestamps cannot be directly reported to the > Linux stack, as it expects 64bits of time. > > To hand

Re: [Intel-wired-lan] [PATCH iwl-next v7 09/12] iavf: refactor iavf_clean_rx_irq to support legacy and flex descriptors

2024-06-08 Thread Simon Horman
On Tue, Jun 04, 2024 at 09:13:57AM -0400, Mateusz Polchlopek wrote: > From: Jacob Keller > > Using VIRTCHNL_VF_OFFLOAD_FLEX_DESC, the iAVF driver is capable of > negotiating to enable the advanced flexible descriptor layout. Add the > flexible NIC layout (RXDID=2) as a member of the Rx descriptor

Re: [Intel-wired-lan] [PATCH iwl-next v7 10/12] iavf: Implement checking DD desc field

2024-06-08 Thread Simon Horman
On Tue, Jun 04, 2024 at 09:13:58AM -0400, Mateusz Polchlopek wrote: > Rx timestamping introduced in PF driver caused the need of refactoring > the VF driver mechanism to check packet fields. > > The function to check errors in descriptor has been removed and from > now only previously set struct f

Re: [Intel-wired-lan] [PATCH iwl-next v7 11/12] iavf: handle set and get timestamps ops

2024-06-08 Thread Simon Horman
On Tue, Jun 04, 2024 at 09:13:59AM -0400, Mateusz Polchlopek wrote: > From: Jacob Keller > > Add handlers for the .ndo_hwtstamp_get and .ndo_hwtstamp_set ops which allow > userspace to request timestamp enablement for the device. This support allows > standard Linux applications to request the ti

Re: [Intel-wired-lan] [PATCH iwl-next v7 12/12] iavf: add support for Rx timestamps to hotpath

2024-06-08 Thread Simon Horman
On Tue, Jun 04, 2024 at 09:14:00AM -0400, Mateusz Polchlopek wrote: > From: Jacob Keller > > Add support for receive timestamps to the Rx hotpath. This support only > works when using the flexible descriptor format, so make sure that we > request this format by default if we have receive timestam

Re: [Intel-wired-lan] [PATCH iwl-next v3 0/3] ice:Support to dump PHY config, FEC

2024-06-08 Thread Samal, Anil
Hi Jacob, Can you please help me with the branch name that I should rebase? Last time I rebased to "dev-queue" branch of "git clone git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git". Let me know, if I should use a different branch for rebasing. Thanks Anil -Original Message

[Intel-wired-lan] [tnguy-next-queue:dev-queue] BUILD SUCCESS 2746dc17cbf54ef20cc09a7ec6862477a326fae1

2024-06-08 Thread kernel test robot
-002-20240608 clang i386 buildonly-randconfig-005-20240608 clang i386 randconfig-001-20240608 clang i386 randconfig-004-20240608 clang i386 randconfig-011-20240608 clang i386 randconfig-012-20240608 clang i386

[Intel-wired-lan] [tnguy-net-queue:dev-queue] BUILD SUCCESS 3480b86d0ad6df1f7fd4978557bc016ad1ed8c64

2024-06-08 Thread kernel test robot
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/net-queue.git dev-queue branch HEAD: 3480b86d0ad6df1f7fd4978557bc016ad1ed8c64 ice: Do not get coalesce settings while in reset elapsed time: 1621m configs tested: 22 configs skipped: 2 The following configs have been built suc

[Intel-wired-lan] [iwl-next v1 1/1] igc: Remove the internal 'eee_advert' field

2024-06-08 Thread Sasha Neftin
Since kernels 'ethtool_keee' structure is in use, the internal 'eee_advert' a field becomes pointless and can be removed. This patch comes to clean up this redundant code. Signed-off-by: Sasha Neftin --- drivers/net/ethernet/intel/igc/igc.h | 1 - drivers/net/ethernet/intel/igc/igc_etht