[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250409103130.43ab4179@kmaincent-XPS-13-7390>
Date: Wed, 9 Apr 2025 10:31:30 +0200
From: Kory Maincent <kory.maincent@...tlin.com>
To: "Russell King (Oracle)" <linux@...linux.org.uk>
Cc: Andrew Lunn <andrew@...n.ch>, Heiner Kallweit <hkallweit1@...il.com>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni
<pabeni@...hat.com>, Marek Behún <kabel@...nel.org>, Richard
Cochran <richardcochran@...il.com>, Thomas Petazzoni
<thomas.petazzoni@...tlin.com>, Maxime Chevallier
<maxime.chevallier@...tlin.com>, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, Vladimir Oltean <vladimir.oltean@....com>
Subject: Re: [PATCH net-next v2 0/2] Add Marvell PHY PTP support
On Tue, 8 Apr 2025 21:38:19 +0100
"Russell King (Oracle)" <linux@...linux.org.uk> wrote:
> On Mon, Apr 07, 2025 at 06:39:14PM +0200, Kory Maincent wrote:
> > On Mon, 7 Apr 2025 17:32:43 +0100
> > "Russell King (Oracle)" <linux@...linux.org.uk> wrote:
> > > I'm preferring to my emails in connection with:
> > >
> > > https://lore.kernel.org/r/ZzTMhGDoi3WcY6MR@shell.armlinux.org.uk
> > >
> > > when I tested your work last time, it seemed that what was merged hadn't
> > > even been tested. In the last email, you said you'd look into it, but I
> > > didn't hear anything further. Have the problems I reported been
> > > addressed?
> >
> > It wasn't merged it was 19th version and it worked and was tested, but not
> > with the best development design. I have replied to you that I will do some
> > change in v20 to address this.
> > https://lore.kernel.org/all/20241113171443.697ac278@kmaincent-XPS-13-7390/
> >
> > It gets finally merged in v21.
>
> Okay, so I'm pleased to report that this now works on the Macchiatobin:
>
> where phc 2 is the mvpp2 clock, and phc 0 is the PHY.
Great, thank you for the testing!
>
> # ethtool -T eth2
> Time stamping parameters for eth2:
> Capabilities:
> hardware-transmit
> software-transmit
> hardware-receive
> software-receive
> software-system-clock
> hardware-raw-clock
> PTP Hardware Clock: 2
> Hardware Transmit Timestamp Modes:
> off
> on
> onestep-sync
> onestep-p2p
> Hardware Receive Filter Modes:
> none
> all
>
> So I guess that means that by default it's using PHC 2, and thus using
> the MVPP2 PTP implementation - which is good, it means that when we add
> Marvell PHY support, this won't switch to the PHY implementation.
Yes.
>
> Now, testing ethtool:
>
> $ ./ethtool --get-hwtimestamp-cfg eth2
> netlink error: Operation not supported
>
> Using ynl:
>
> # ./ynl/cli.py --spec netlink/specs/ethtool.yaml --no-schema --dump
> tsconfig-get --json '{"header":{"dev-name":"eth2"}}' []
>
> So, It's better, something still isn't correct as there's no
> configuration. Maybe mvpp2 needs updating first? If that's the case,
> then we're not yet in a position to merge PHY PTP support.
Indeed mvpp2 has not been update to support the ndo_hwtstamp_get/set NDOs.
Vlad had made some work to update all net drivers to these NDOs but he never
send it mainline:
https://github.com/vladimiroltean/linux/commits/ndo-hwtstamp-v9
I have already try to ping him on this but without success.
Vlad any idea on when you could send your series upstream?
Regards,
--
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
Powered by blists - more mailing lists