On Sat, Apr 22, 2017 at 12:28 AM, Sinan Kaya <[email protected]> wrote: > GED driver is currently set up as a platform driver. On modern operating > systems, most of the drivers are compiled as kernel modules. It is possible > that a GED interrupt event is received and the driver such as GHES/GPIO/I2C > to service it is not available yet. To accommodate this use case, delay > GED driver load to the late init phase. > > Signed-off-by: Sinan Kaya <[email protected]> > --- > drivers/acpi/evged.c | 8 +++++++- > 1 file changed, 7 insertions(+), 1 deletion(-) > > diff --git a/drivers/acpi/evged.c b/drivers/acpi/evged.c > index 46f0603..30e638b 100644 > --- a/drivers/acpi/evged.c > +++ b/drivers/acpi/evged.c > @@ -151,4 +151,10 @@ static int ged_probe(struct platform_device *pdev) > .acpi_match_table = ACPI_PTR(ged_acpi_ids), > }, > }; > -builtin_platform_driver(ged_driver); > + > +static __init int ged_init(void) > +{ > + return platform_driver_register(&ged_driver); > +} > + > +late_initcall(ged_init);
Does this fix the problem? What about if the module in question is loaded after running late_initcalls? Thanks, Rafael
