On Saturday 23 May 2015 03:05:36 Pali Rohár wrote: > On Saturday 23 May 2015 00:53:16 Dmitry Torokhov wrote: > > On Thu, May 21, 2015 at 7:06 PM, Valdis Kletnieks > > > > <Valdis.Kletnieks@xxxxxx> wrote: > > > So after I made both config variables =y, the resulting kernel > > > built, but died a glorious death at boot. > > > > I guess if both are built-in then, according to link order, > > dell-laptop starts first, before dell-rbtn, and dies in > > dell_rbtn_notifier_register() in call to > > driver_for_each_device(&rbtn_driver.drv, ...) because rbtn_driver > > has not been registered yet and thus half-initlalized. > > > > Thanks. > > pr_debug() messages could be useful... but no idea if we can get > them. > > Is there any way to fix that dependency race condition? Could > driver_attach() function call help? Or what about using late_initcall() instead module_init() for driver dell-laptop.ko? By default module_init() for static linked modules is macro for device_initcall() which is called before late_initcall(), right? -- Pali Rohár pali.rohar@xxxxxxxxx
Attachment:
signature.asc
Description: This is a digitally signed message part.
