From: Jason Reeder <jreeder@ti.com>
To: Ravi Gunasekaran <r-gunasekaran@ti.com>, <s-vadapalli@ti.com>,
<rogerq@kernel.org>
Cc: <davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <richardcochran@gmail.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<srk@ti.com>, <ed.trexel@hp.com>, <oem-support@audinate.com>
Subject: Re: [PATCH net] net: ethernet: ti: am65-cpts: Fix PTPv1 message type on TX packets
Date: Fri, 19 Apr 2024 11:03:26 -0600 [thread overview]
Message-ID: <1cf9c10b-5cf3-412a-83a5-e6891a18c2f1@ti.com> (raw)
In-Reply-To: <20240419080547.10682-1-r-gunasekaran@ti.com>
On 4/19/24 02:05, Ravi Gunasekaran wrote:
> From: Jason Reeder <jreeder@ti.com>
>
> The CPTS, by design, captures the messageType (Sync, Delay_Req, etc.)
> field from the second nibble of the PTP header which is defined in the
> PTPv2 (1588-2008) specification. In the PTPv1 (1588-2002) specification
> the first two bytes of the PTP header are defined as the versionType
> which is always 0x0001. This means that any PTPv1 packets that are
> tagged for TX timestamping by the CPTS will have their messageType set
> to 0x0 which corresponds to a Sync message type. This causes issues
> when a PTPv1 stack is expecting a Delay_Req (messageType: 0x1)
> timestamp that never appears.
>
> Fix this by checking if the ptp_class of the timestamped TX packet is
> PTP_CLASS_V1 and then matching the PTP sequence ID to the stored
> sequence ID in the skb->cb data structure. If the sequence IDs match
> and the packet is of type PTPv1 then there is a chance that the
> messageType has been incorrectly stored by the CPTS so overwrite the
> messageType stored by the CPTS with the messageType from the skb->cb
> data structure. This allows the PTPv1 stack to receive TX timestamps
> for Delay_Req packets which are necessary to lock onto a PTP Leader.
>
> Signed-off-by: Jason Reeder <jreeder@ti.com>
> Signed-off-by: Ravi Gunasekaran <r-gunasekaran@ti.com>
> ---
> drivers/net/ethernet/ti/am65-cpts.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/net/ethernet/ti/am65-cpts.c b/drivers/net/ethernet/ti/am65-cpts.c
> index c66618d91c28..f89716b1cfb6 100644
> --- a/drivers/net/ethernet/ti/am65-cpts.c
> +++ b/drivers/net/ethernet/ti/am65-cpts.c
> @@ -784,6 +784,11 @@ static bool am65_cpts_match_tx_ts(struct am65_cpts *cpts,
> struct am65_cpts_skb_cb_data *skb_cb =
> (struct am65_cpts_skb_cb_data *)skb->cb;
>
> + if ((ptp_classify_raw(skb) & PTP_CLASS_V1) &&
> + ((mtype_seqid & AM65_CPTS_EVENT_1_SEQUENCE_ID_MASK) ==
> + (skb_cb->skb_mtype_seqid & AM65_CPTS_EVENT_1_SEQUENCE_ID_MASK)))
> + mtype_seqid = skb_cb->skb_mtype_seqid;
> +
> if (mtype_seqid == skb_cb->skb_mtype_seqid) {
> u64 ns = event->timestamp;
>
>
> base-commit: a35e92ef04c07bd473404b9b73d489aea19a60a8
++ Ed Trexel at HP and the Audinate support team for visibility and
'Tested-by' tags.
Jason Reeder
next prev parent reply other threads:[~2024-04-19 17:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 8:05 Ravi Gunasekaran
2024-04-19 17:03 ` Jason Reeder [this message]
2024-04-23 10:01 ` Paolo Abeni
2024-04-23 11:06 ` Ravi Gunasekaran
2024-04-23 11:44 ` Paolo Abeni
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=1cf9c10b-5cf3-412a-83a5-e6891a18c2f1@ti.com \
--to=jreeder@ti.com \
--cc=davem@davemloft.net \
--cc=ed.trexel@hp.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oem-support@audinate.com \
--cc=pabeni@redhat.com \
--cc=r-gunasekaran@ti.com \
--cc=richardcochran@gmail.com \
--cc=rogerq@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=srk@ti.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
all inboxes | Powered by JetHome®