From: Daniel Machon <daniel.machon@microchip.com>
To: Quentin Freimanis <quentin@q-lab.dev>
Cc: <netdev@vger.kernel.org>, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
"Jakub Kicinski" <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
<UNGLinuxDriver@microchip.com>,
"Richard Cochran" <richardcochran@gmail.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net v2] net: sparx5: start the TOD counters on non-PTP lan969x variants
Date: Mon, 5 Oct 2026 11:57:35 +0200 [thread overview]
Message-ID: <20261005095735.jzzlcdf6oljxpdpx@DEN-DL-M70577> (raw)
In-Reply-To: <20261005052826.14251-1-quentin@q-lab.dev>
> Currently the base non-PTP-capable lan969x variants don't forward any
> Ethernet frames:
>
> $ ip link set eth10 up
>
> $ ip addr add 10.0.0.54/24 dev eth10
>
> $ ping 10.0.0.1
> PING 10.0.0.1 (10.0.0.1): 56 data bytes
>
> --- 10.0.0.1 ping statistics ---
> 7 packets transmitted, 0 packets received, 100% packet loss
>
> $ cat /proc/interrupts | grep fdma
> 20: 0 GIC-0 120 Level sparx5-fdma
>
> $ ip -s link show dev eth10
> RX: bytes packets errors dropped missed mcast
> 20828 102 0 0 0 72
> TX: bytes packets errors dropped carrier collsns
> 0 0 0 0 0 0
>
> Testing showed that starting the domain 0 TOD counter gets networking
> working again, but start all three for consistency with the PTP variants.
Tested-by: Daniel Machon <daniel.machon@microchip.com>
Reviewed-by: Daniel Machon <daniel.machon@microchip.com>
Thank you for the patch! :-)
next prev parent reply other threads:[~2026-10-05 9:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-05 5:28 [PATCH net v2] net: sparx5: start the TOD counters on non-PTP lan969x variants Quentin Freimanis
2026-10-05 9:57 ` Daniel Machon [this message]
2026-10-07 0:20 ` patchwork-bot+netdevbpf
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=20261005095735.jzzlcdf6oljxpdpx@DEN-DL-M70577 \
--to=daniel.machon@microchip.com \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quentin@q-lab.dev \
--cc=richardcochran@gmail.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