ig4: ensure that drivers always attach in correct order
Use DRIVER_MODULE_ORDERED(SI_ORDER_ANY) so that ig4's ACPI attachment happens after iicbus and acpi_iicbus drivers are registered. I have seen a problem where iicbus attached under ig4 instead of acpi_iicbus when ig4.ko was loaded with kldload. I believe that that happened because ig4 driver was a first driver to register, it attached and created an iicbus child. Then iicbus driver was registered and, since it was the only driver that could attach to the iicbus child device, it did exactly that. After that acpi_iicbus driver was registered. It would be able to attach to the iicbus device, but it was already attached, so nothing happened. MFC after: 2 weeks
This commit is contained in:
parent
dd5f96c48d
commit
7a451e61ab
@ -192,5 +192,6 @@ static driver_t ig4iic_acpi_driver = {
|
|||||||
sizeof(struct ig4iic_softc),
|
sizeof(struct ig4iic_softc),
|
||||||
};
|
};
|
||||||
|
|
||||||
DRIVER_MODULE(ig4iic, acpi, ig4iic_acpi_driver, ig4iic_devclass, 0, 0);
|
DRIVER_MODULE_ORDERED(ig4iic, acpi, ig4iic_acpi_driver, ig4iic_devclass, 0, 0,
|
||||||
|
SI_ORDER_ANY);
|
||||||
MODULE_DEPEND(ig4iic, acpi, 1, 1, 1);
|
MODULE_DEPEND(ig4iic, acpi, 1, 1, 1);
|
||||||
|
Loading…
x
Reference in New Issue
Block a user