On Wed, 7 Apr 2021 17:50:46 +0200 Heiner Kallweit wrote:
> Resume callback of the PHY driver is called after the one for the MAC
> driver. The PHY driver resume callback calls phy_init_hw(), and this is
> potentially problematic if the MAC driver calls phy_start() in its resume
> callback. One issu
On 07.04.2021 17:50, Heiner Kallweit wrote:
> Resume callback of the PHY driver is called after the one for the MAC
> driver. The PHY driver resume callback calls phy_init_hw(), and this is
> potentially problematic if the MAC driver calls phy_start() in its resume
> callback. One issue was reporte
--Original Message-
>> From: Heiner Kallweit
>> Sent: 2021年4月7日 23:51
>> To: Andrew Lunn ; Russell King - ARM Linux
>> ; Jakub Kicinski ; David Miller
>> ; Fugang Duan
>> Cc: netdev@vger.kernel.org; Joakim Zhang
>> Subject: [PATCH net-next 0/3] net
; David Miller
> ; Fugang Duan
> Cc: netdev@vger.kernel.org; Joakim Zhang
> Subject: [PATCH net-next 0/3] net: make PHY PM ops a no-op if MAC driver
> manages PHY PM
>
> Resume callback of the PHY driver is called after the one for the MAC driver.
> The PHY driver resume callb
Resume callback of the PHY driver is called after the one for the MAC
driver. The PHY driver resume callback calls phy_init_hw(), and this is
potentially problematic if the MAC driver calls phy_start() in its resume
callback. One issue was reported with the fec driver and a KSZ8081 PHY
which seems
