[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <07bb218b-2a3e-482a-951f-a84aac498bb3@intel.com>
Date: Tue, 15 Apr 2025 14:14:31 -0700
From: Jacob Keller <jacob.e.keller@...el.com>
To: Milena Olech <milena.olech@...el.com>, <intel-wired-lan@...ts.osuosl.org>
CC: <netdev@...r.kernel.org>, <anthony.l.nguyen@...el.com>,
<przemyslaw.kitszel@...el.com>, Alexander Lobakin
<aleksander.lobakin@...el.com>, Emil Tantilov <emil.s.tantilov@...el.com>,
Pavan Kumar Linga <pavan.kumar.linga@...el.com>
Subject: Re: [Intel-wired-lan] [PATCH v11 iwl-next 09/11] idpf: add Tx
timestamp capabilities negotiation
On 4/14/2025 3:45 AM, Milena Olech wrote:
> Tx timestamp capabilities are negotiated for the uplink Vport.
> Driver receives information about the number of available Tx timestamp
> latches, the size of Tx timestamp value and the set of indexes used
> for Tx timestamping.
>
> Add function to get the Tx timestamp capabilities and parse the uplink
> vport flag.
>
> Reviewed-by: Alexander Lobakin <aleksander.lobakin@...el.com>
> Co-developed-by: Emil Tantilov <emil.s.tantilov@...el.com>
> Signed-off-by: Emil Tantilov <emil.s.tantilov@...el.com>
> Co-developed-by: Pavan Kumar Linga <pavan.kumar.linga@...el.com>
> Signed-off-by: Pavan Kumar Linga <pavan.kumar.linga@...el.com>
> Signed-off-by: Milena Olech <milena.olech@...el.com>
> ---
> v10 -> v11: use one lock for both free/in-use latches lists, allocate
> each latch separately
> v7 -> v8: refactor idpf_for_each_vport, change a function that
> checks if Tx timestamp for a given vport is enabled
> v2 -> v3: revert changes in idpf_for_each_vport, fix minor issues
> v1 -> v2: change the idpf_for_each_vport macro
>
Reviewed-by: Jacob Keller <jacob.e.keller@...el.com>
Powered by blists - more mailing lists