+18
−4
Loading
Commit 11a78b79 ("ARM: OMAP: MPUIO wake updates") registers the omap_mpuio_driver from omap_mpuio_init(), which is called from omap_gpio_probe(). However, it neither makes sense to register drivers from probe() callbacks of other drivers, nor does the driver core allow registering drivers with a device lock already being held. The latter was revealed by commit dc23806a ("driver core: enforce device_lock for driver_match_device()") leading to a potential deadlock condition described in [1]. Additionally, the omap_mpuio_driver is never unregistered from the driver core, even if the module is unloaded. Hence, register the omap_mpuio_driver from the module initcall and unregister it in module_exit(). Link: https://lore.kernel.org/lkml/DFU7CEPUSG9A.1KKGVW4HIPMSH@kernel.org/ [1] Fixes: dc23806a ("driver core: enforce device_lock for driver_match_device()") Fixes: 11a78b79 ("ARM: OMAP: MPUIO wake updates") Reviewed-by:Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by:
Danilo Krummrich <dakr@kernel.org> Reviewed-by:
Rafael J. Wysocki (Intel) <rafael@kernel.org> Link: https://patch.msgid.link/20260127201725.35883-1-dakr@kernel.org Signed-off-by:
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>