[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230228141630.64d5ef63@kmaincent-XPS-13-7390>
Date: Tue, 28 Feb 2023 14:16:30 +0100
From: Köry Maincent <kory.maincent@...tlin.com>
To: "Russell King (Oracle)" <linux@...linux.org.uk>
Cc: Richard Cochran <richardcochran@...il.com>, andrew@...n.ch,
davem@...emloft.net, f.fainelli@...il.com, hkallweit1@...il.com,
kuba@...nel.org, netdev@...r.kernel.org,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
Maxime Chevallier <maxime.chevallier@...tlin.com>
Subject: Re: [PATCH RFC net-next] net: phy: add Marvell PHY PTP support
[multicast/DSA issues]
On Tue, 28 Feb 2023 12:07:09 +0000
"Russell King (Oracle)" <linux@...linux.org.uk> wrote:
> So yes, it's a nice idea to support multiple hardware timestamps, but
> I think that's an entirely separate problem to solving the current
> issue, which is a blocking issue to adding support for PTP on some
> platforms.
Alright, Richard can I continue your work on it and send new revisions of your
patch series or do you prefer to continue on your own?
Also your series rise the question of which timestamping should be the default,
MAC or PHY, without breaking any past or future compatibilities.
There is question of using Kconfig or devicetree but each of them seems to have
drawbacks:
https://lore.kernel.org/netdev/ad4a8d3efbeaacf241a19bfbca5976f9@walle.cc/
Do you or Russell have any new thought about it?
Regards,
Köry
Powered by blists - more mailing lists