[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZMe6ykS6s9a/en8r@hoboy.vegasvil.org>
Date: Mon, 31 Jul 2023 06:44:42 -0700
From: Richard Cochran <richardcochran@...il.com>
To: Johannes Zink <j.zink@...gutronix.de>
Cc: Giuseppe Cavallaro <peppe.cavallaro@...com>,
Alexandre Torgue <alexandre.torgue@...s.st.com>,
Jose Abreu <joabreu@...opsys.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
Russell King <linux@...linux.org.uk>,
patchwork-jzi@...gutronix.de, netdev@...r.kernel.org,
linux-stm32@...md-mailman.stormreply.com,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
kernel@...gutronix.de, kernel test robot <lkp@...el.com>
Subject: Re: [PATCH v2] net: stmmac: correct MAC propagation delay
On Mon, Jul 31, 2023 at 09:00:29AM +0200, Johannes Zink wrote:
> I cannot tell for sure either, since I have datasheets for the i.MX8MP only.
> Maybe Kurt has some insights here, as he has additional hardware available
> for testing?
Maybe give the folks who make the dwc a call to clarify?
> Nevertheless, I am going to add a guard to only use the correction codepath
> on i.MX8MP in v3 for the time being, we can add other hardware later
> trivially if they support doing this.
Sure.
Thanks,
Richard
Powered by blists - more mailing lists