[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dc45261a-403d-260c-fae6-1956f873ebbc@gmail.com>
Date: Fri, 9 Apr 2021 11:23:33 +0200
From: Heiner Kallweit <hkallweit1@...il.com>
To: Jakub Kicinski <kuba@...nel.org>,
David Miller <davem@...emloft.net>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Joakim Zhang <qiangqing.zhang@....com>,
Russell King - ARM Linux <linux@...linux.org.uk>,
Andrew Lunn <andrew@...n.ch>
Subject: Re: [PATCH net-next 0/3] net: make PHY PM ops a no-op if MAC driver
manages PHY PM
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 reported with the fec driver and a KSZ8081 PHY
> which seems to become unstable if a soft reset is triggered during aneg.
>
> The new flag allows MAC drivers to indicate that they take care of
> suspending/resuming the PHY. Then the MAC PM callbacks can handle
> any dependency between MAC and PHY PM.
>
> Heiner Kallweit (3):
> net: phy: make PHY PM ops a no-op if MAC driver manages PHY PM
> net: fec: use mac-managed PHY PM
> r8169: use mac-managed PHY PM
>
> drivers/net/ethernet/freescale/fec_main.c | 3 +++
> drivers/net/ethernet/realtek/r8169_main.c | 3 +++
> drivers/net/phy/phy_device.c | 6 ++++++
> include/linux/phy.h | 2 ++
> 4 files changed, 14 insertions(+)
>
This series has status "Needs ACK". For which part an ACK is needed?
Regarding the fec driver:
The mail to Fugang, the current fec maintainer, bounced and Joakim
confirmed that he left NXP. Joakim will take over, see
https://patchwork.kernel.org/project/netdevbpf/patch/20210409091145.27488-1-qiangqing.zhang@nxp.com/
Joakim also tested the patch.
Heiner
Powered by blists - more mailing lists