Thread (15 messages) flat view 15 messages, 4 authors, 2021-06-28

RE: [PATCH net-next V1 3/4] net: stmmac: Reconfigure the PHY WOL settings in stmmac_resume()

From: Voon, Weifeng <hidden>
Date: 2021-06-28 07:48:57
Also in: linux-arm-kernel, lkml

quoted
I would like to rephase the commit message to make things clear:

After PHY received a magic packet, the PHY WOL event will be
triggered. At the same time, the "Magic Packet Match Detected" bit is
set. In order for the PHY WOL event to be triggered again, the WOL
event status of "Magic Packet Match Detected" bit needs to be cleared.
When the PHY is in polling mode, the WOL event status needs to be
manually cleared.

Ethtool settings will remain with WOL enabled after a S3/S4 suspend
resume cycle as expected. Hence, the driver should reconfigure the PHY
settings to reenable/disable WOL depending on the ethtool WOL settings
in the MAC resume flow.
The PHY set_wol flow would clear the WOL event status.
I would still argue that making use of a WoL interrupts and PHY polling is
just wrong. But i assume you cannot fix this? You have a hardware design
error?

The problem with this solution is you need to modify every MAC driver using
the Marvell PHY. It does not scale.

Please try to find a solution within phylib or the marvell driver.
Something which will work for any broken setup which is using WoL
interrupts combined with polling.
Yes, I would not able to fix this as the PHY WOL event signal pin is connected
directly to the PMC. And, I do not have the info why the HW is designed in
this way. 

But, I totally agreed that this solution is not scalable. We will drop this
patch from this patchset for v2. We will find another solution and most
probably in phylib as this behavior most likely will be similar across all
other PHYs.

Weifeng
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help