[lkml]   [2011]   [Jul]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] drivercore: Add driver probe deferral mechanism
On Tue, Jul 5, 2011 at 10:11 AM, Kay Sievers <> wrote:
> On Tue, Jul 5, 2011 at 17:50, Greg KH <> wrote:
>> I wonder if doing this all from a workqueue in the first place is going
>> to cause problems as probe isn't normally done this way at all.
> Yeah, I would expect unforeseen problems with the async thread too.
> It's probably all solvable, but it sounds troublesome to find out if
> things go wrong.
> We have sync hooks (BUS_NOTIFY_*) where any kind of code can subscribe
> to when devices get added or get bound to a driver. Can't the code
> that relies on later hookups to already existing devices/bindings not
> just plug into that?

I tried that. It resulted in a lot of complexity that each driver
needs to implement correctly which is why I started looking for a
different way to go about it.


 \ /
  Last update: 2011-07-05 18:31    [W:0.072 / U:1.076 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site