[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <57D5F4E2-409F-4709-A9E7-299AF28E4AB3@timebeat.app>
Date: Sat, 23 Apr 2022 11:26:34 +0100
From: Lasse Johnsen <lasse@...ebeat.app>
To: Jonathan Lemon <jonathan.lemon@...il.com>
Cc: Richard Cochran <richardcochran@...il.com>, netdev@...r.kernel.org,
Gordon Hollingworth <gordon@...pberrypi.com>,
Ahmad Byagowi <clk@...com>,
Florian Fainelli <f.fainelli@...il.com>,
Andrew Lunn <andrew@...n.ch>,
Heiner Kallweit <hkallweit1@...il.com>,
Russell King <linux@...linux.org.uk>,
bcm-kernel-feedback-list@...adcom.com,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>
Subject: Re: [PATCH net-next v2] net: phy: broadcom: 1588 support on
bcm54210pe
I have reviewed the documentation again, and I am inclined to agree with you. I will modify driver to use in-band RX timestamps. It looks like TX timestamps can also be updated on the fly to allow for one-step operation.
> On 22 Apr 2022, at 19:20, Jonathan Lemon <jonathan.lemon@...il.com> wrote:
>
> Uhm, I have inbound timestamps working for RX on an RPI CM4.
Powered by blists - more mailing lists