From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: "Bastien Curutchet (Schneider Electric)"
<bastien.curutchet@bootlin.com>,
Woojung Huh <woojung.huh@microchip.com>,
UNGLinuxDriver@microchip.com, Andrew Lunn <andrew@lunn.ch>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Richard Cochran <richardcochran@gmail.com>,
Simon Horman <horms@kernel.org>
Cc: "Pascal Eberhard" <pascal.eberhard@se.com>,
"Miquèl Raynal" <miquel.raynal@bootlin.com>,
"Thomas Petazzoni" <thomas.petazzoni@bootlin.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 5/8] net: dsa: microchip: Add KSZ8463 tail tag handling
Date: Thu, 15 Jan 2026 18:05:43 +0100 [thread overview]
Message-ID: <722dcba9-d9ae-43ba-b1bf-1d577a882bef@bootlin.com> (raw)
In-Reply-To: <20260115-ksz8463-ptp-v1-5-bcfe2830cf50@bootlin.com>
Hi Bastien,
On 15/01/2026 16:57, Bastien Curutchet (Schneider Electric) wrote:
> KSZ8463 uses the KSZ9893 DSA TAG driver. However, the KSZ8463 doesn't
> use the tail tag to convey timestamps to the host as KSZ9893 does. It
> uses the reserved fields in the PTP header instead.
[ ... ]
> +static struct sk_buff *ksz8463_rcv(struct sk_buff *skb, struct net_device *dev)
> +{
> + unsigned int len = KSZ_EGRESS_TAG_LEN;
> + struct ptp_header *ptp_hdr;
> + unsigned int ptp_class;
> + unsigned int port;
> + ktime_t tstamp;
> + u8 *tag;
> +
> + if (skb_linearize(skb))
> + return NULL;
> +
> + /* Tag decoding */
> + tag = skb_tail_pointer(skb) - KSZ_EGRESS_TAG_LEN;
> + port = tag[0] & KSZ8463_TAIL_TAG_EG_PORT_M;
> +
> + __skb_push(skb, ETH_HLEN);
> + ptp_class = ptp_classify_raw(skb);
> + __skb_pull(skb, ETH_HLEN);
> + if (ptp_class == PTP_CLASS_NONE)
> + goto common_rcv;
> +
> + ptp_hdr = ptp_parse_header(skb, ptp_class);
> + if (ptp_hdr) {
> + tstamp = ksz_decode_tstamp(get_unaligned_be32(&ptp_hdr->reserved2));
> + KSZ_SKB_CB(skb)->tstamp = tstamp;
As it is using a reserved field, is it OK to leave this field as-is when forwarding
this skb to userspace, or should it be zeroed first ?
Maxime
next prev parent reply other threads:[~2026-01-15 17:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 15:56 [PATCH net-next 0/8] net: dsa: microchip: Add PTP support for the KSZ8463 Bastien Curutchet (Schneider Electric)
2026-01-15 15:57 ` [PATCH net-next 1/8] net: dsa: microchip: Add support for KSZ8463 global irq Bastien Curutchet (Schneider Electric)
2026-01-15 15:57 ` [PATCH net-next 2/8] net: dsa: microchip: Decorrelate IRQ domain from port Bastien Curutchet (Schneider Electric)
2026-01-15 15:57 ` [PATCH net-next 3/8] net: dsa: microchip: Decorrelate msg_irq index from IRQ bit offset Bastien Curutchet (Schneider Electric)
2026-01-15 15:57 ` [PATCH net-next 4/8] net: dsa: microchip: Add support for KSZ8463's PTP interrupts Bastien Curutchet (Schneider Electric)
2026-01-15 23:18 ` kernel test robot
2026-01-15 15:57 ` [PATCH net-next 5/8] net: dsa: microchip: Add KSZ8463 tail tag handling Bastien Curutchet (Schneider Electric)
2026-01-15 17:05 ` Maxime Chevallier [this message]
2026-01-16 7:08 ` Bastien Curutchet
2026-01-20 17:17 ` Simon Horman
2026-01-22 12:59 ` Bastien Curutchet
2026-01-23 10:12 ` Simon Horman
2026-01-15 15:57 ` [PATCH net-next 6/8] net: dsa: microchip: Enable Ethernet PTP detection Bastien Curutchet (Schneider Electric)
2026-01-15 15:57 ` [PATCH net-next 7/8] net: dsa: microchip: Adapt port offset for KSZ8463's PTP register Bastien Curutchet (Schneider Electric)
2026-01-15 15:57 ` [PATCH net-next 8/8] net: dsa: microchip: Add two-step PTP support for KSZ8463 Bastien Curutchet (Schneider Electric)
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=722dcba9-d9ae-43ba-b1bf-1d577a882bef@bootlin.com \
--to=maxime.chevallier@bootlin.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=bastien.curutchet@bootlin.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=pascal.eberhard@se.com \
--cc=richardcochran@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=woojung.huh@microchip.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