From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
devicetree <devicetree@vger.kernel.org>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Fabien Parent <fparent@baylibre.com>,
Iyappan Subramanian <iyappan@os.amperecomputing.com>,
Quan Nguyen <quan@os.amperecomputing.com>,
Frank Rowand <frowand.list@gmail.com>,
Bartosz Golaszewski <brgl@bgdev.pl>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Jakub Kicinski <kuba@kernel.org>,
Yisen Zhuang <yisen.zhuang@huawei.com>,
Vivien Didelot <vivien.didelot@gmail.com>,
Tom Lendacky <thomas.lendacky@amd.com>,
Andrew Perepech <andrew.perepech@mediatek.com>,
Stephane Le Provost <stephane.leprovost@mediatek.com>,
Keyur Chudgar <keyur@os.amperecomputing.com>,
Jassi Brar <jaswinder.singh@linaro.org>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
"moderated list:ARM/Mediatek SoC..."
<linux-mediatek@lists.infradead.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Salil Mehta <salil.mehta@huawei.com>,
netdev <netdev@vger.kernel.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Microchip Linux Driver Support <UNGLinuxDriver@microchip.com>,
Mark Brown <broonie@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Pedro Tsai <pedro.tsai@mediatek.com>,
"David S . Miller" <davem@davemloft.net>,
Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: [PATCH 09/15] net: phy: delay PHY driver probe until PHY registration
Date: Wed, 24 Jun 2020 17:50:16 +0100 [thread overview]
Message-ID: <20200624165016.GA1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <f806586d-a6d7-99af-bba4-d1e7d28be192@gmail.com>
On Wed, Jun 24, 2020 at 09:06:28AM -0700, Florian Fainelli wrote:
> On 6/24/2020 6:48 AM, Bartosz Golaszewski wrote:
> > I didn't expect to open such a can of worms...
> >
> > This has evolved into several new concepts being proposed vs my
> > use-case which is relatively simple. The former will probably take
> > several months of development, reviews and discussions and it will
> > block supporting the phy supply on pumpkin boards upstream. I would
> > prefer not to redo what other MAC drivers do (phy-supply property on
> > the MAC node, controlling it from the MAC driver itself) if we've
> > already established it's wrong.
>
> You are not new to Linux development, so none of this should come as a
> surprise to you. Your proposed solution has clearly short comings and is
> a hack, especially around the PHY_ID_NONE business to get a phy_device
> only then to have the real PHY device ID. You should also now that "I
> need it now because my product deliverable depends on it" has never been
> received as a valid argument to coerce people into accepting a solution
> for which there are at review time known deficiencies to the proposed
> approach.
It /is/ a generic issue. The same problem exists for AMBA Primecell
devices, and that code has an internal deferred device list that it
manages. See drivers/amba/bus.c, amba_deferred_retry_func(),
amba_device_try_add(), and amba_device_add().
As we see more devices gain this property, it needs to be addressed
in a generic way, rather than coming up with multiple bus specific
implementations.
Maybe struct bus_type needs a method to do the preparation to add
a device (such as reading IDs etc), which is called by device_add().
If that method returns -EPROBE_DEFER, the device gets added to a
deferred list, which gets retried when drivers are successfully
probed. Possible maybe?
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-06-24 16:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200622093744.13685-1-brgl@bgdev.pl>
[not found] ` <20200622093744.13685-15-brgl@bgdev.pl>
[not found] ` <20200622132921.GI1551@shell.armlinux.org.uk>
[not found] ` <CAMRc=Me1r3Mzfg3-gTsGk4rEtvB=P9ESkn9q=c7z0Q=YQDsw2A@mail.gmail.com>
[not found] ` <20200623094252.GS1551@shell.armlinux.org.uk>
[not found] ` <CAMpxmJVP9db-4-AA4e1JkEfrajvJ4s0T6zo5+oFzpJHRBcuSsg@mail.gmail.com>
[not found] ` <20200623095646.GT1551@shell.armlinux.org.uk>
2020-06-23 16:27 ` [PATCH 14/15] net: phy: add PHY regulator support Bartosz Golaszewski
2020-06-24 16:57 ` Russell King - ARM Linux admin
2020-06-24 18:12 ` Russell King - ARM Linux admin
[not found] ` <20200622093744.13685-2-brgl@bgdev.pl>
2020-06-23 18:54 ` [PATCH 01/15] net: phy: arrange headers in mdio_bus.c alphabetically Florian Fainelli
[not found] ` <20200622093744.13685-3-brgl@bgdev.pl>
2020-06-23 18:56 ` [PATCH 02/15] net: phy: arrange headers in mdio_device.c alphabetically Florian Fainelli
[not found] ` <20200622093744.13685-4-brgl@bgdev.pl>
2020-06-23 18:57 ` [PATCH 03/15] net: phy: arrange headers in phy_device.c alphabetically Florian Fainelli
[not found] ` <20200622093744.13685-5-brgl@bgdev.pl>
2020-06-23 18:59 ` [PATCH 04/15] net: mdio: add a forward declaration for reset_control to mdio.h Florian Fainelli
[not found] ` <20200622093744.13685-6-brgl@bgdev.pl>
2020-06-23 19:14 ` [PATCH 05/15] net: phy: reset the PHY even if probe() is not implemented Florian Fainelli
2020-06-24 16:22 ` Bartosz Golaszewski
[not found] ` <20200622093744.13685-7-brgl@bgdev.pl>
2020-06-23 19:16 ` [PATCH 06/15] net: phy: mdio: reset MDIO devices " Florian Fainelli
[not found] ` <20200622093744.13685-13-brgl@bgdev.pl>
2020-06-23 19:39 ` [PATCH 12/15] dt-bindings: mdio: add phy-supply property to ethernet phy node Florian Fainelli
[not found] ` <20200622093744.13685-10-brgl@bgdev.pl>
[not found] ` <20200622133940.GL338481@lunn.ch>
[not found] ` <20200622135106.GK4560@sirena.org.uk>
2020-06-23 19:49 ` [PATCH 09/15] net: phy: delay PHY driver probe until PHY registration Florian Fainelli
2020-06-24 9:43 ` Mark Brown
2020-06-24 13:48 ` Bartosz Golaszewski
2020-06-24 16:06 ` Florian Fainelli
2020-06-24 16:35 ` Bartosz Golaszewski
2020-06-24 16:50 ` Russell King - ARM Linux admin [this message]
2020-06-24 18:59 ` Robin Murphy
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=20200624165016.GA1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew.perepech@mediatek.com \
--cc=andrew@lunn.ch \
--cc=bgolaszewski@baylibre.com \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=claudiu.manoil@nxp.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=fparent@baylibre.com \
--cc=frowand.list@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=ilias.apalodimas@linaro.org \
--cc=iyappan@os.amperecomputing.com \
--cc=jaswinder.singh@linaro.org \
--cc=keyur@os.amperecomputing.com \
--cc=kuba@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=pedro.tsai@mediatek.com \
--cc=quan@os.amperecomputing.com \
--cc=robh+dt@kernel.org \
--cc=salil.mehta@huawei.com \
--cc=stephane.leprovost@mediatek.com \
--cc=thomas.lendacky@amd.com \
--cc=vivien.didelot@gmail.com \
--cc=vladimir.oltean@nxp.com \
--cc=yisen.zhuang@huawei.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).