[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <167506381644.14069.1519780033829172123.git-patchwork-notify@kernel.org>
Date: Mon, 30 Jan 2023 07:30:16 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Andrey Konovalov <andrey.konovalov@...aro.org>
Cc: vkoul@...nel.org, bhupesh.sharma@...aro.org, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
andrew@...n.ch, robh@...nel.org, alexandre.torgue@...s.st.com,
peppe.cavallaro@...com, joabreu@...opsys.com,
mcoquelin.stm32@...il.com, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org
Subject: Re: [PATCH 0/1] net: stmmac: do not stop RX_CLK in Rx LPI state for
qcs404 SoC
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@...emloft.net>:
On Fri, 27 Jan 2023 00:35:38 +0300 you wrote:
> This is a different, for one SoC only solution to the issue described below
> vs a generic one submitted earlier [1].
>
> On my qcs404 based board the ethernet MAC has issues with handling
> Rx LPI exit / Rx LPI entry interrupts.
>
> When in LPI mode the "refresh transmission" is received, the driver may
> see both "Rx LPI exit", and "Rx LPI entry" bits set in the single read from
> GMAC4_LPI_CTRL_STATUS register (vs "Rx LPI exit" first, and "Rx LPI entry"
> then). In this case an interrupt storm happens: the LPI interrupt is
> triggered every few microseconds - with all the status bits in the
> GMAC4_LPI_CTRL_STATUS register being read as zeros. This interrupt storm
> continues until a normal non-zero status is read from GMAC4_LPI_CTRL_STATUS
> register (single "Rx LPI exit", or "Tx LPI exit").
>
> [...]
Here is the summary with links:
- [1/1] net: stmmac: do not stop RX_CLK in Rx LPI state for qcs404 SoC
https://git.kernel.org/netdev/net/c/54aa39a513db
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists