From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Anton Nadezhdin <anton.nadezhdin@intel.com>,
intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, anthony.l.nguyen@intel.com,
richardcochran@gmail.com, Milena Olech <milena.olech@intel.com>,
Aleksandr Loktionov <aleksandr.loktionov@intel.com>,
Jakub Kicinski <kuba@kernel.org>,
Willem de Bruijn <willemb@google.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next 2/2] idpf: add direct method for disciplining Tx timestamping
Date: Tue, 2 Sep 2025 12:27:29 +0100 [thread overview]
Message-ID: <26c0cd9c-ad24-4b71-9a1a-d046b94d9333@linux.dev> (raw)
In-Reply-To: <20250902105321.5750-3-anton.nadezhdin@intel.com>
On 02/09/2025 11:50, Anton Nadezhdin wrote:
> From: Milena Olech <milena.olech@intel.com>
>
> Currently IDPF supports only mailbox access to PHC operations and
> Tx timestamping, however the driver shall also be able to handle direct
> access. The difference is that PHC/timestamps actions are performed
> directly, through BAR registers, instead of sending a virtchnl message to
> CP. Registers offsets are negotiated with the CP during the capabilities
> negotiation.
>
> Signed-off-by: Milena Olech <milena.olech@intel.com>
> Co-developed-by: Anton Nadezhdin <anton.nadezhdin@intel.com>
> Signed-off-by: Anton Nadezhdin <anton.nadezhdin@intel.com>
> Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
[...]
> -static void idpf_tx_read_tstamp(struct idpf_tx_queue *txq, struct sk_buff *skb)
> +static void idpf_tx_read_tstamp(struct idpf_tx_queue *txq, struct sk_buff *skb,
> + u32 buf_id)
> {
> struct idpf_ptp_vport_tx_tstamp_caps *tx_tstamp_caps;
> - struct idpf_ptp_tx_tstamp_status *tx_tstamp_status;
> + struct idpf_ptp_tx_tstamp_status *tx_tstamp_status = NULL;
this breaks reverse x-mass tree aligment...
> + enum idpf_ptp_access access;
> + int err;
WARNING: multiple messages have this Message-ID (diff)
From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Anton Nadezhdin <anton.nadezhdin@intel.com>,
intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, anthony.l.nguyen@intel.com,
richardcochran@gmail.com, Milena Olech <milena.olech@intel.com>,
Aleksandr Loktionov <aleksandr.loktionov@intel.com>,
Jakub Kicinski <kuba@kernel.org>,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH iwl-next 2/2] idpf: add direct method for disciplining Tx timestamping
Date: Tue, 2 Sep 2025 12:27:29 +0100 [thread overview]
Message-ID: <26c0cd9c-ad24-4b71-9a1a-d046b94d9333@linux.dev> (raw)
In-Reply-To: <20250902105321.5750-3-anton.nadezhdin@intel.com>
On 02/09/2025 11:50, Anton Nadezhdin wrote:
> From: Milena Olech <milena.olech@intel.com>
>
> Currently IDPF supports only mailbox access to PHC operations and
> Tx timestamping, however the driver shall also be able to handle direct
> access. The difference is that PHC/timestamps actions are performed
> directly, through BAR registers, instead of sending a virtchnl message to
> CP. Registers offsets are negotiated with the CP during the capabilities
> negotiation.
>
> Signed-off-by: Milena Olech <milena.olech@intel.com>
> Co-developed-by: Anton Nadezhdin <anton.nadezhdin@intel.com>
> Signed-off-by: Anton Nadezhdin <anton.nadezhdin@intel.com>
> Reviewed-by: Aleksandr Loktionov <aleksandr.loktionov@intel.com>
[...]
> -static void idpf_tx_read_tstamp(struct idpf_tx_queue *txq, struct sk_buff *skb)
> +static void idpf_tx_read_tstamp(struct idpf_tx_queue *txq, struct sk_buff *skb,
> + u32 buf_id)
> {
> struct idpf_ptp_vport_tx_tstamp_caps *tx_tstamp_caps;
> - struct idpf_ptp_tx_tstamp_status *tx_tstamp_status;
> + struct idpf_ptp_tx_tstamp_status *tx_tstamp_status = NULL;
this breaks reverse x-mass tree aligment...
> + enum idpf_ptp_access access;
> + int err;
next prev parent reply other threads:[~2025-09-02 11:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 10:50 [Intel-wired-lan] [PATCH iwl-next 0/2] idpf: add direct access for PHC control Anton Nadezhdin
2025-09-02 10:50 ` Anton Nadezhdin
2025-09-02 10:50 ` [Intel-wired-lan] [PATCH iwl-next 1/2] idpf: add direct access to discipline the main timer Anton Nadezhdin
2025-09-02 10:50 ` Anton Nadezhdin
2025-09-02 11:05 ` [Intel-wired-lan] " Vadim Fedorenko
2025-09-02 11:05 ` Vadim Fedorenko
2025-09-11 16:02 ` [Intel-wired-lan] " Naman Gulati
2025-09-11 16:02 ` Naman Gulati
2025-09-02 10:50 ` [Intel-wired-lan] [PATCH iwl-next 2/2] idpf: add direct method for disciplining Tx timestamping Anton Nadezhdin
2025-09-02 10:50 ` Anton Nadezhdin
2025-09-02 11:27 ` Vadim Fedorenko [this message]
2025-09-02 11:27 ` Vadim Fedorenko
2025-09-02 14:06 ` [Intel-wired-lan] " kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=26c0cd9c-ad24-4b71-9a1a-d046b94d9333@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=aleksandr.loktionov@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=anton.nadezhdin@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=milena.olech@intel.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=willemb@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.