Re: [RFC PATCH net-next 1/3] net: phy: don't bind genphy in phy_attach_direct if the specific driver defers probe
From: Vladimir Oltean <olteanv@gmail.com>
Date: 2021-09-02 21:39:58
Also in:
lkml, netdev
On Thu, Sep 02, 2021 at 10:33:03PM +0100, Russell King (Oracle) wrote:
That's probably an unreliable indicator. DPAA2 has weirdness in the way it can dynamically create and destroy network interfaces, which does lead to problems with the rtnl lock. I've been carrying a patch from NXP for this for almost two years now, which NXP still haven't submitted: http://git.armlinux.org.uk/cgit/linux-arm.git/commit/?h=cex7&id=a600f2ee50223e9bcdcf86b65b4c427c0fd425a4 ... and I've no idea why that patch never made mainline. I need it to avoid the stated deadlock on SolidRun Honeycomb platforms when creating additional network interfaces for the SFP cages in userspace.
Ah, nice, I've copied that broken logic for the dpaa2-switch too: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=d52ef12f7d6c016f3b249db95af33f725e3dd065 So why don't you send the patch? I can send it too if you want to, one for the switch and one for the DPNI driver.