Messages in this thread | | | From | Grant Likely <> | Date | Tue, 5 Jul 2011 10:33:15 -0600 | Subject | Re: [PATCH] drivercore: Add driver probe deferral mechanism |
| |
On Tue, Jul 5, 2011 at 10:11 AM, Kay Sievers <kay.sievers@vrfy.org> wrote: > On Tue, Jul 5, 2011 at 17:50, Greg KH <gregkh@suse.de> 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.
I think it is worth solving though since the feature is important. I can certainly block out the deferral code with a Kconfig symbol so that it only gets built when a driver selects CONFIG_PROBE_DEFERRAL. That would keep the code out of x86 kernels while us embedded folks iron out the bugs.
g.
| |