[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140831175243.GB17827@core.coreip.homeip.net>
Date: Sun, 31 Aug 2014 10:52:43 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Tejun Heo <tj@...nel.org>
Cc: "Luis R. Rodriguez" <mcgrof@...not-panic.com>,
gregkh@...uxfoundation.org, falcon@...zu.com, tiwai@...e.de,
arjan@...ux.intel.com, linux-kernel@...r.kernel.org,
oleg@...hat.com, akpm@...ux-foundation.org,
penguin-kernel@...ove.sakura.ne.jp, joseph.salisbury@...onical.com,
bpoirier@...e.de, "Luis R. Rodriguez" <mcgrof@...e.com>
Subject: Re: [RFC v1 0/3] driver-core: add asynch module loading support
On Sun, Aug 31, 2014 at 07:05:26AM -0400, Tejun Heo wrote:
> On Sun, Aug 31, 2014 at 07:02:00AM -0400, Tejun Heo wrote:
> > So, something like the following. A couple things to note
> >
> > * driver_attach() can never fail but is marked with __must_check. We
> > prolly should change it to void.
> >
> > * Old/weird userspace which depends on insmod to wait for device
> > probing might choke and the new behavior might need to be switched
> > somehow (sysctl, insmod param or whatever).
>
> One more thing.
>
> * Use of ordered workqueue probably isn't necessary and using
> system_unbound_wq should be fine.
>
For my use case (touchpad taking long time to initialize) I explicitly do not
want it to keep order of initialization. I want to make sure the rest of the
kernel continues initialization while touchpad device resets.
Thanks.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists