From: Michael Ellerman <mpe@ellerman.id.au>
To: Scott Wood <scottwood@freescale.com>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>
Cc: devicetree@vger.kernel.org, linux-acpi@vger.kernel.org,
Arnd Bergmann <arnd@arndb.de>,
Stephen Warren <swarren@wwwdotorg.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Walleij <linus.walleij@linaro.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Mark Brown <broonie@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Alan Stern <stern@rowland.harvard.edu>,
Hu Mingkai-B21284 <Mingkai.Hu@freescale.com>,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 22/22] of/platform: Defer probes of registered devices
Date: Thu, 22 Oct 2015 11:34:48 +1100 [thread overview]
Message-ID: <1445474088.30295.5.camel@ellerman.id.au> (raw)
In-Reply-To: <1445406845.701.55.camel@freescale.com>
On Wed, 2015-10-21 at 00:54 -0500, Scott Wood wrote:
> On Mon, 2015-09-21 at 16:03 +0200, Tomeu Vizoso wrote:
> > Instead of trying to match and probe platform and AMBA devices right
> > after each is registered, delay their probes until device_initcall_sync.
> >
> > This means that devices will start probing once all built-in drivers
> > have registered, and after all platform and AMBA devices from the DT
> > have been registered already.
> >
> > This allows us to prevent deferred probes by probing dependencies on
> > demand.
> >
> > Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
> > ---
> >
> > Changes in v4:
> > - Also defer probes of AMBA devices registered from the DT as they can
> > also request resources.
> >
> > drivers/of/platform.c | 11 ++++++++---
> > 1 file changed, 8 insertions(+), 3 deletions(-)
>
> This breaks arch/powerpc/sysdev/fsl_pci.c. The PCI bus is an OF platform
> device, and it must be probed before pcibios_init() which is a
> subsys_initcall(), or else the PCI bus never gets scanned.
Ah right. This is presumably why I'm not seeing any PCI devices on my p5020ds
with linux-next.
cheers
prev parent reply other threads:[~2015-10-22 0:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1442844182-27787-1-git-send-email-tomeu.vizoso@collabora.com>
[not found] ` <1442844182-27787-23-git-send-email-tomeu.vizoso@collabora.com>
2015-10-21 5:54 ` [PATCH v6 22/22] of/platform: Defer probes of registered devices Scott Wood
2015-10-21 13:44 ` Rob Herring
2015-10-21 22:51 ` Scott Wood
2015-10-22 13:04 ` Tomeu Vizoso
2015-10-22 21:27 ` Scott Wood
2015-10-24 13:51 ` Rafael J. Wysocki
2015-10-28 14:40 ` Tomeu Vizoso
2015-10-29 4:17 ` Rob Herring
2015-10-29 16:06 ` Scott Wood
2015-10-22 0:34 ` Michael Ellerman [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=1445474088.30295.5.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=Mingkai.Hu@freescale.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=javier@osg.samsung.com \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=scottwood@freescale.com \
--cc=stern@rowland.harvard.edu \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=tomeu.vizoso@collabora.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).