From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Tomeu Vizoso <tomeu.vizoso@collabora.com>,
Rob Herring <robherring2@gmail.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Stephen Warren <swarren@wwwdotorg.org>,
Linus Walleij <linus.walleij@linaro.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-kernel@vger.kernel.org" <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>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v3 01/18] platform: delay OF device-driver matches until late_initcall
Date: Fri, 7 Aug 2015 20:06:31 +0300 [thread overview]
Message-ID: <55C4E597.1010701@ti.com> (raw)
In-Reply-To: <CAAObsKBapFqzr+4YEXJfcJWMd+tkaBqYbGiFTntHStAP=+P-_Q@mail.gmail.com>
On 08/07/2015 10:11 AM, Tomeu Vizoso wrote:
> On 6 August 2015 at 22:19, Rob Herring <robherring2@gmail.com> wrote:
>> On Thu, Aug 6, 2015 at 9:11 AM, Tomeu Vizoso <tomeu.vizoso@collabora.com> wrote:
>>> Delay matches of platform devices with OF nodes until late_initcall,
>>> when we are sure that all built-in drivers have been registered already.
>>> This is needed to prevent deferred probes because of some drivers not
>>> having registered yet.
>>>
>>> The reason why only platform devices are delayed is that some other
>>> devices are expected to be probed earlier than late_initcall, for
>>> example, the system PNP driver needs to probe its devices in
>>> fs_initcall.
>>>
>>> Additionally, only platform devices with OF nodes are delayed because
>>> some machines may depend on oter platform devices being registered at
>>> specific times.
>>
>> How do we know that these probes occur before the unused clocks and
>> regulators are turned off? Just getting lucky (as is deferred probe)?
>> Can we do this one level earlier so we have a level left to do things
>> after probe.
>
> Those are already late_initcall_sync so I guess we're fine.
I wouldn't be so sure :(
FYI:
http://git.ti.com/ti-linux-kernel/ti-linux-kernel/commit/763d643bbfc0f445c6685c541fcae3c370e4314a
--
regards,
-grygorii
next prev parent reply other threads:[~2015-08-07 17:06 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 14:11 [PATCH v3 0/18] On-demand device probing Tomeu Vizoso
2015-08-06 14:11 ` [PATCH v3 01/18] platform: delay OF device-driver matches until late_initcall Tomeu Vizoso
[not found] ` <1438870315-18689-2-git-send-email-tomeu.vizoso-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2015-08-06 20:19 ` Rob Herring
[not found] ` <CAL_Jsq+GLMZe-f6qEi=7i1YrrWc6k99RpGkOyCd5KkYDiyt0QA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-08-07 7:11 ` Tomeu Vizoso
2015-08-07 17:06 ` Grygorii Strashko [this message]
2015-08-09 13:03 ` Tomeu Vizoso
2015-08-10 10:25 ` Mark Brown
2015-09-04 5:46 ` Tomeu Vizoso
2015-08-14 19:09 ` Grygorii Strashko
2015-09-04 8:05 ` Tomeu Vizoso
2015-08-06 14:11 ` [PATCH v3 02/18] of/platform: add of_platform_probe Tomeu Vizoso
2015-08-07 12:19 ` Mark Brown
2015-08-11 9:37 ` Tomeu Vizoso
2015-09-07 12:31 ` Tomeu Vizoso
2015-09-11 9:57 ` Mark Brown
2015-09-11 14:06 ` Tomeu Vizoso
2015-09-11 15:35 ` Mark Brown
2015-09-15 13:08 ` Tomeu Vizoso
2015-08-06 14:11 ` [PATCH v3 03/18] gpio: Probe GPIO drivers on demand Tomeu Vizoso
2015-08-06 14:11 ` [PATCH v3 04/18] gpio: Probe pinctrl devices " Tomeu Vizoso
2015-08-06 14:11 ` [PATCH v3 05/18] regulator: core: Reduce critical area in _regulator_get Tomeu Vizoso
2015-08-07 12:07 ` Mark Brown
2015-08-06 14:11 ` [PATCH v3 06/18] regulator: core: Probe regulators on demand Tomeu Vizoso
2015-08-07 12:09 ` Mark Brown
2015-08-07 13:58 ` Rob Herring
2015-08-06 14:11 ` [PATCH v3 07/18] drm: Probe panels " Tomeu Vizoso
2015-08-06 14:11 ` [PATCH v3 08/18] drm/tegra: Probe dpaux devices " Tomeu Vizoso
2015-08-06 14:11 ` [PATCH v3 09/18] i2c: core: Probe i2c adapters and " Tomeu Vizoso
2015-08-06 14:11 ` [PATCH v3 10/18] pwm: Probe PWM chip " Tomeu Vizoso
2015-08-06 14:11 ` [PATCH v3 11/18] backlight: Probe backlight " Tomeu Vizoso
2015-08-06 14:11 ` [PATCH v3 12/18] usb: phy: Probe phy " Tomeu Vizoso
2015-08-06 14:11 ` [PATCH v3 13/18] clk: Probe clk providers " Tomeu Vizoso
2015-08-06 14:11 ` [PATCH v3 15/18] phy: core: Probe phy " Tomeu Vizoso
[not found] ` <1438870315-18689-1-git-send-email-tomeu.vizoso-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2015-08-06 14:11 ` [PATCH v3 14/18] pinctrl: Probe pinctrl devices " Tomeu Vizoso
2015-08-06 14:11 ` [PATCH v3 16/18] dma: of: Probe DMA controllers " Tomeu Vizoso
2015-08-06 14:11 ` [PATCH v3 17/18] power-supply: Probe power supplies " Tomeu Vizoso
2015-08-06 14:11 ` [PATCH v3 18/18] ASoC: core: Probe components " Tomeu Vizoso
2015-08-06 20:14 ` [PATCH v3 0/18] On-demand device probing Rob Herring
2015-08-07 6:55 ` Tomeu Vizoso
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=55C4E597.1010701@ti.com \
--to=grygorii.strashko@ti.com \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--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=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=robherring2@gmail.com \
--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).