Thread (29 messages) 29 messages, 4 authors, 2015-07-17

Re: [PATCH v2 01/12] device: property: delay device-driver matches

From: Rafael J. Wysocki <hidden>
Date: 2015-07-16 23:41:20
Also in: alsa-devel, dri-devel, linux-acpi, linux-fbdev, linux-gpio, linux-pwm, lkml

Hi Mark,

On Thu, Jul 16, 2015 at 10:23 PM, Mark Brown [off-list ref] wrote:
On Wed, Jul 01, 2015 at 11:40:56AM +0200, Tomeu Vizoso wrote:
quoted
Delay matches of platform devices 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 dependencies' drivers not
having registered yet.
I have to say I'm still not 100% clear that special casing platform
devices makes sense here - I can see that platform devices are usually
the first devices to instantiate but there are other kinds of devices
and it's not obvious what the benefit of specifically picking out
platform devices as opposed to just deferring all devices is.
Some existing devices cannot be deferred without redesigning things quite a bit.

What I was talking about, though, was to use an opt-in mechanism for
that which could be set for all platform devices, for example, by
default, but it might be set for other bus types too if that's useful.

Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help