[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZME88hOgNug+PFga@hoboy.vegasvil.org>
Date: Wed, 26 Jul 2023 08:34:10 -0700
From: Richard Cochran <richardcochran@...il.com>
To: Marc Kleine-Budde <mkl@...gutronix.de>
Cc: Jakub Kicinski <kuba@...nel.org>,
Johannes Zink <j.zink@...gutronix.de>,
linux-kernel@...r.kernel.org, kernel@...gutronix.de,
netdev@...r.kernel.org, linux-stm32@...md-mailman.stormreply.com,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Russell King <linux@...linux.org.uk>,
kernel test robot <lkp@...el.com>,
Eric Dumazet <edumazet@...gle.com>,
Jose Abreu <joabreu@...opsys.com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Giuseppe Cavallaro <peppe.cavallaro@...com>,
Paolo Abeni <pabeni@...hat.com>,
"David S. Miller" <davem@...emloft.net>,
linux-arm-kernel@...ts.infradead.org, patchwork-jzi@...gutronix.de
Subject: Re: [PATCH v2] net: stmmac: correct MAC propagation delay
On Wed, Jul 26, 2023 at 08:04:37AM +0200, Marc Kleine-Budde wrote:
> At least the datasheet of the IP core tells to read the MAC delay from
> the IP core (1), add the PHY delay (2) and the clock domain crossing
> delay (3) and write it to the time stamp correction register.
That is great, until they change the data sheet. Really, this happens.
Thanks,
Richard
Powered by blists - more mailing lists