From: Simon Horman <horms@kernel.org>
To: "Bastien Curutchet (Schneider Electric)" <bastien.curutchet@bootlin.com>
Cc: "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>,
"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: Tue, 20 Jan 2026 17:17:30 +0000 [thread overview]
Message-ID: <aW-4qgp0mGNPNiau@horms.kernel.org> (raw)
In-Reply-To: <20260115-ksz8463-ptp-v1-5-bcfe2830cf50@bootlin.com>
On Thu, Jan 15, 2026 at 04:57:04PM +0100, 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.
>
> Add a KSZ8463-specifig DSA_TAG driver to handle KSZ8463 timestamps.
> There is no information in the tail tag to distinguish PTP packets from
> others so use the ptp_classify_raw() helper to find the PTP packets and
> extract the timestamp from their PTP headers.
>
> Signed-off-by: Bastien Curutchet (Schneider Electric) <bastien.curutchet@bootlin.com>
...
> diff --git a/net/dsa/tag_ksz.c b/net/dsa/tag_ksz.c
> index 9170a0148cc43b4213ec4bd8e81d338589671f23..635679402f8a96b29536a91988346a8825bae976 100644
> --- a/net/dsa/tag_ksz.c
> +++ b/net/dsa/tag_ksz.c
> @@ -16,6 +16,7 @@
> #define KSZ9477_NAME "ksz9477"
> #define KSZ9893_NAME "ksz9893"
> #define LAN937X_NAME "lan937x"
> +#define KSZ8463_NAME "ksz8463"
>
> /* Typically only one byte is used for tail tag. */
> #define KSZ_PTP_TAG_LEN 4
> @@ -383,6 +384,108 @@ static const struct dsa_device_ops ksz9893_netdev_ops = {
> DSA_TAG_DRIVER(ksz9893_netdev_ops);
> MODULE_ALIAS_DSA_TAG_DRIVER(DSA_TAG_PROTO_KSZ9893, KSZ9893_NAME);
>
> +#define KSZ8463_TAIL_TAG_PRIO GENMASK(4, 3)
> +#define KSZ8463_TAIL_TAG_EG_PORT_M GENMASK(2, 0)
> +
> +static void ksz8463_xmit_timestamp(struct dsa_port *dp, struct sk_buff *skb)
> +{
> + struct ksz_tagger_private *priv;
> + struct ptp_header *ptp_hdr;
> + unsigned int ptp_type;
> + u32 tstamp_raw = 0;
> + s64 correction;
> +
> + priv = ksz_tagger_private(dp->ds);
> +
> + if (!test_bit(KSZ_HWTS_EN, &priv->state))
> + return;
> +
> + if (!KSZ_SKB_CB(skb)->update_correction)
> + return;
> +
> + ptp_type = KSZ_SKB_CB(skb)->ptp_type;
> + ptp_hdr = ptp_parse_header(skb, ptp_type);
> + if (!ptp_hdr)
> + return;
> +
> + correction = (s64)get_unaligned_be64(&ptp_hdr->correction);
> +
> + if (correction < 0) {
> + struct timespec64 ts;
> +
> + ts = ns_to_timespec64(-correction >> 16);
> + tstamp_raw = ((ts.tv_sec & 3) << 30) | ts.tv_nsec;
> +
> + ptp_hdr->reserved2 = tstamp_raw;
I think that you need to assign a be32 rather than a u32 to reserved2.
Flagged by Sparse [1].
[1] This particular commit, from Al Viro's tree:
https://git.kernel.org/pub/scm/linux/kernel/git/viro/sparse.git/commit/?id=2634e39bf02697a18fece057208150362c985992
To address this mess:
https://lore.kernel.org/all/bf5b9a62-a120-421e-908d-1404c42e0b60@kernel.org/
> + }
> +}
...
next prev parent reply other threads:[~2026-01-20 17:17 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
2026-01-16 7:08 ` Bastien Curutchet
2026-01-20 17:17 ` Simon Horman [this message]
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=aW-4qgp0mGNPNiau@horms.kernel.org \
--to=horms@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=bastien.curutchet@bootlin.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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