From: "Köry Maincent" <kory.maincent@bootlin.com>
To: "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: andrew@lunn.ch, davem@davemloft.net, f.fainelli@gmail.com,
hkallweit1@gmail.com, kuba@kernel.org, netdev@vger.kernel.org,
richardcochran@gmail.com,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Maxime Chevallier <maxime.chevallier@bootlin.com>
Subject: Re: [PATCH RFC net-next] net: phy: add Marvell PHY PTP support [multicast/DSA issues]
Date: Thu, 27 Apr 2023 17:13:06 +0200 [thread overview]
Message-ID: <20230427171306.2bfd824a@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <Y/zKJUHUhEgXjKFG@shell.armlinux.org.uk>
Hello Russell,
On Mon, 27 Feb 2023 15:20:05 +0000
"Russell King (Oracle)" <linux@armlinux.org.uk> wrote:
> On Mon, Feb 27, 2023 at 03:40:37PM +0100, Köry Maincent wrote:
> > Hello RMK,
> >
> > > Hence why I'm at the point of giving up; I don't see that PTP will be
> > > of very limited benefit on my network with all these issues, and in
> > > any case, NTP has been "good enough" for the last 20+ years. Given
> > > that only a limited number of machines will be able to implement PTP
> > > support anyway, NTP will have to run along side it.
> >
> > I see this patch has been abandoned.
> > I am testing it with a ZynqMP board (macb ethernet) and it seems to more or
> > less work. It got tx timestamp timeout at initialization but after some
> > times (~20 seconds) ptp4l manages to set it working. Also the IEEE 802.3
> > network PTP mode is not working, it constantly throw rx timestamp overrun
> > errors.
> > I will aim at fixing these issues and adding support to interrupts. It
> > would be good to have it accepted mainline. What do you think is missing
> > for that?
>
> It isn't formally abandoned, but is permanently on-hold as merging
> Marvell PHY PTP support into mainline _will_ regress the superior PTP
> support on the Macchiatobin platform for the reasons outlined in:
>
> https://lore.kernel.org/netdev/20200729220748.GW1605@shell.armlinux.org.uk/
>
> Attempting to fix this problem was basically rejected by the PTP
> maintainer, and thus we're at a deadlock over the issue, and Marvell
> PHY PTP support can never be merged into mainline.
As we are currently moving forward on PTP core to resolve this issue, I would
like to investigate your PHY PTP patch in parallel. Indeed it does not work very
well on my side.
The PTP UDP v4 and v6 work only if I add "--tx_timestamp_timeout 20" and the
PTP IEEE 802.3 (802.1AS) does not work at all.
On PTP IEEE 802.3 network transport ("ptp4l -2") I get continuously rx timestamp
overrun:
Marvell 88E1510 ff0d0000.ethernet-ffffffff:01: rx timestamp overrun (5)
Marvell 88E1510 ff0d0000.ethernet-ffffffff:01: rx timestamp overrun (5)
I know it's been a long time but does it ring a bell on your memory?
next prev parent reply other threads:[~2023-04-27 15:13 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 16:26 [PATCH RFC net-next] net: phy: add Marvell PHY PTP support Russell King
2020-07-15 18:38 ` Andrew Lunn
2020-07-15 18:56 ` Russell King - ARM Linux admin
2020-07-16 11:33 ` Russell King - ARM Linux admin
2020-07-16 20:53 ` Richard Cochran
2020-07-16 20:48 ` Richard Cochran
2020-07-17 7:54 ` Kurt Kanzenbach
2020-07-18 2:24 ` Richard Cochran
2020-07-20 14:21 ` Richard Cochran
2020-07-20 14:37 ` Kurt Kanzenbach
2020-07-26 23:48 ` Russell King - ARM Linux admin
2020-07-29 10:58 ` Russell King - ARM Linux admin
2020-07-29 13:19 ` Richard Cochran
2020-07-29 13:28 ` Russell King - ARM Linux admin
2020-07-29 22:07 ` Russell King - ARM Linux admin
2020-07-29 22:53 ` Vladimir Oltean
2020-07-30 15:53 ` Richard Cochran
2020-07-30 18:38 ` Russell King - ARM Linux admin
2020-07-30 19:32 ` Richard Cochran
2020-07-30 19:44 ` Russell King - ARM Linux admin
2020-07-30 11:06 ` [PATCH RFC net-next] net: phy: add Marvell PHY PTP support [multicast/DSA issues] Russell King - ARM Linux admin
2020-07-30 11:54 ` Russell King - ARM Linux admin
2020-07-30 12:47 ` Russell King - ARM Linux admin
2023-02-27 14:40 ` Köry Maincent
2023-02-27 15:20 ` Russell King (Oracle)
2023-02-27 17:30 ` Köry Maincent
2023-02-27 17:42 ` Russell King (Oracle)
2023-02-27 19:45 ` Richard Cochran
2023-02-27 20:09 ` Russell King (Oracle)
2023-02-27 20:19 ` Richard Cochran
2023-02-28 12:07 ` Russell King (Oracle)
2023-02-28 13:16 ` Köry Maincent
2023-02-28 13:36 ` Russell King (Oracle)
2023-02-28 14:50 ` Köry Maincent
2023-02-28 15:16 ` Richard Cochran
2023-02-28 15:33 ` Andrew Lunn
2023-02-28 21:13 ` Richard Cochran
2023-02-28 16:27 ` Russell King (Oracle)
2023-02-28 16:44 ` Michael Walle
2023-02-28 16:58 ` Russell King (Oracle)
2023-02-28 20:13 ` Michael Walle
2023-02-28 21:11 ` Richard Cochran
2023-02-28 21:24 ` Richard Cochran
2023-02-28 22:26 ` Jakub Kicinski
2023-02-28 22:40 ` Russell King (Oracle)
2023-02-28 22:59 ` Jakub Kicinski
2023-03-01 16:04 ` Köry Maincent
2023-03-02 4:36 ` Richard Cochran
2023-03-02 11:49 ` Russell King (Oracle)
2023-03-02 16:49 ` Jakub Kicinski
2023-03-02 17:06 ` Köry Maincent
2023-03-02 17:23 ` Jakub Kicinski
2023-03-03 13:12 ` Köry Maincent
2023-03-03 23:28 ` Jakub Kicinski
2023-03-02 17:26 ` Russell King (Oracle)
2023-03-03 10:20 ` Michael Walle
2023-03-03 13:20 ` Andrew Lunn
2023-03-03 13:34 ` Köry Maincent
2023-03-03 13:59 ` Andrew Lunn
2023-03-03 14:03 ` Russell King (Oracle)
2023-03-03 16:34 ` Andrew Lunn
2023-03-03 17:32 ` Richard Cochran
2023-03-03 17:35 ` Richard Cochran
2023-03-03 23:40 ` Jakub Kicinski
2023-03-02 21:28 ` Richard Cochran
2023-03-02 21:19 ` Richard Cochran
2023-04-27 15:13 ` Köry Maincent [this message]
2023-04-27 16:50 ` Andrew Lunn
2023-04-28 8:51 ` Köry Maincent
2020-07-30 15:50 ` Richard Cochran
2020-07-31 14:41 ` Andrew Lunn
2023-03-02 10:37 ` [PATCH RFC net-next] net: phy: add Marvell PHY PTP support Köry Maincent
2023-03-02 17:38 ` Russell King (Oracle)
2023-03-02 21:35 ` Richard Cochran
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=20230427171306.2bfd824a@kmaincent-XPS-13-7390 \
--to=kory.maincent@bootlin.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
--cc=thomas.petazzoni@bootlin.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;
as well as URLs for NNTP newsgroup(s).