From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Milind Parab <mparab@cadence.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: phylink: propagate phy_attach_direct() return code
Date: Sun, 15 Dec 2019 07:43:15 +0000 [thread overview]
Message-ID: <20191215074314.GZ25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20191214202745.649bbed2@cakuba.netronome.com>
On Sat, Dec 14, 2019 at 08:27:45PM -0800, Jakub Kicinski wrote:
> On Thu, 12 Dec 2019 17:16:12 +0000, Russell King wrote:
> > of_phy_attach() hides the return value of phy_attach_direct(), forcing
> > us to return a "generic" ENODEV error code that is indistinguishable
> > from the lack-of-phy-property case.
> >
> > Switch to using of_phy_find_device() to find the PHY device, and then
> > propagating any phy_attach_direct() error back to the caller.
> >
> > Link: https://lore.kernel.org/lkml/20191210113829.GT25745@shell.armlinux.org.uk
> > Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
>
> Applied thanks, the ref counting is not entirely obvious to a layman.
> In your reply to Milind you said he can immediately of_node_put()
> because the phy_dev is never deferenced in his code, but here it looks
> like it is actually - the reference used to be given up after attach is
> done, now its given up before attach_direct is called.
The refcount is on the device_node - once we've got the phy device
itself (or failed to) we're not using the device_node anymore, so
we can put it directly after the of_phy_find_device() call.
>
> But I don't know how the refcounting here works, so applied, and on the
> off chance the code is wrong follow up will be fine.
>
> > diff --git a/drivers/net/phy/phylink.c b/drivers/net/phy/phylink.c
> > index f7c660bf99d1..8d20cf3ba0b7 100644
> > --- a/drivers/net/phy/phylink.c
> > +++ b/drivers/net/phy/phylink.c
> > @@ -859,14 +859,17 @@ int phylink_of_phy_connect(struct phylink *pl, struct device_node *dn,
> > return 0;
> > }
> >
> > - phy_dev = of_phy_attach(pl->netdev, phy_node, flags,
> > - pl->link_interface);
> > + phy_dev = of_phy_find_device(phy_node);
> > /* We're done with the phy_node handle */
> > of_node_put(phy_node);
> > -
> > if (!phy_dev)
> > return -ENODEV;
> >
> > + ret = phy_attach_direct(pl->netdev, phy_dev, flags,
> > + pl->link_interface);
> > + if (ret)
> > + return ret;
> > +
> > ret = phylink_bringup_phy(pl, phy_dev, pl->link_config.interface);
> > if (ret)
> > phy_detach(phy_dev);
>
>
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 12.1Mbps down 622kbps up
According to speedtest.net: 11.9Mbps down 500kbps up
prev parent reply other threads:[~2019-12-15 7:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 17:16 [PATCH net-next] net: phylink: propagate phy_attach_direct() return code Russell King
2019-12-15 4:27 ` Jakub Kicinski
2019-12-15 7:43 ` Russell King - ARM Linux admin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191215074314.GZ25745@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=mparab@cadence.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.