From: Ratheesh Kannoth <rkannoth@marvell.com>
To: <davem@davemloft.net>, <kuba@kernel.org>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<sbhatta@marvell.com>, <sgoutham@marvell.com>, <zyta@marvell.com>
Cc: <andrew+netdev@lunn.ch>, <edumazet@google.com>,
<pabeni@redhat.com>, <richardcochran@gmail.com>,
Sai Krishna <saikrishnag@marvell.com>
Subject: Re: [PATCH v2 net] octeontx2: fix PTP RX enable notification on VF
Date: Mon, 24 Aug 2026 12:01:32 +0530 [thread overview]
Message-ID: <aovlRCN217lBuFY4@rkannoth-OptiPlex-7090> (raw)
In-Reply-To: <20260820044439.2592441-1-rkannoth@marvell.com>
On 2026-08-20 at 10:14:39, Ratheesh Kannoth (rkannoth@marvell.com) wrote:
> From: Sai Krishna <saikrishnag@marvell.com>
>
> When a VF enables PTP RX timestamping, CGX prepends an 8-byte timestamp
> header to each packet. The parent PF and its VFs must adjust their RX
> data offset before that happens, but enabling PTP RX only configured CGX
> and never notified the PF or VFs.
>
> Add a CGX_PTP_RX_INFO mailbox upcall from AF to PF when RX timestamping
> is enabled or disabled. On receipt, the PF records the state and forwards
> it to active VFs. Handle the upcall on the VF mailbox path so the
> notification completes correctly.
>
> Use the asynchronous upcall pattern (wait for zero, then send) on both
> AF-to-PF and PF-to-VF paths, and serialize PF-to-VF delivery with the
> mailbox lock, consistent with link-event notification.
>
> Fixes: 421572175ba5 ("octeontx2-af: Support to enable/disable HW timestamping")
> Signed-off-by: Sai Krishna <saikrishnag@marvell.com>
> Signed-off-by: Ratheesh Kannoth <rkannoth@marvell.com>
>
> 2.43.0
>
Will address sashiko comments in v3
pw-bot: changes-requested
prev parent reply other threads:[~2026-08-24 6:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 4:44 [PATCH v2 net] octeontx2: fix PTP RX enable notification on VF Ratheesh Kannoth
2026-08-24 6:31 ` Ratheesh Kannoth [this message]
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=aovlRCN217lBuFY4@rkannoth-OptiPlex-7090 \
--to=rkannoth@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=saikrishnag@marvell.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=zyta@marvell.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox