[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220104014215.GA20062@hoboy.vegasvil.org>
Date: Mon, 3 Jan 2022 17:42:15 -0800
From: Richard Cochran <richardcochran@...il.com>
To: "Russell King (Oracle)" <linux@...linux.org.uk>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
Andrew Lunn <andrew@...n.ch>,
David Miller <davem@...emloft.net>,
Grygorii Strashko <grygorii.strashko@...com>,
Jakub Kicinski <kuba@...nel.org>,
Joakim Zhang <qiangqing.zhang@....com>,
Kurt Kanzenbach <kurt@...utronix.de>,
Miroslav Lichvar <mlichvar@...hat.com>,
Vladimir Oltean <vladimir.oltean@....com>
Subject: Re: [PATCH RFC V1 net-next 3/4] net: Let the active time stamping
layer be selectable.
On Mon, Jan 03, 2022 at 11:53:57PM +0000, Russell King (Oracle) wrote:
> On Mon, Jan 03, 2022 at 03:25:54PM -0800, Richard Cochran wrote:
> > Make the sysfs knob writable, and add checks in the ioctl and time
> > stamping paths to respect the currently selected time stamping layer.
> >
> > Signed-off-by: Richard Cochran <richardcochran@...il.com>
>
> As I stated for patch 2, this patch will break mvpp2 PTP support,
> since as soon as we bind a PHY, whether or not it supports PTP, you
> will switch "selected_timestamping_layer" to be PHY mode PTP, and
> direct all PTP calls to the PHY layer whether or not the PHY has
> PTP support, away from the MAC layer.
Oh, that was a brain fart of mine.
I'll amend that to switch selected_timestamping_layer only if the PHY
does support time stamping.
IMO, the default should be PHY because up until now the PHY layer was
prefered.
Or would you say the MAC layer should take default priority?
(that may well break some existing systems)
Thanks,
Richard
Powered by blists - more mailing lists