From: Rafael J. Wysocki Date: Thu, 5 Jun 2025 15:04:11 +0000 (+0200) Subject: intel_idle: Use subsys_initcall_sync() for initialization X-Git-Tag: v6.16-rc2~11^2^2~5 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=c0f691388992c708436ab5f6e810865be6ddf5c6;p=thirdparty%2Flinux.git intel_idle: Use subsys_initcall_sync() for initialization It is not necessary to wait until the device_initcall() stage with intel_idle initialization. All of its dependencies are met after all subsys_initcall()s have run, so subsys_initcall_sync() can be used for initializing it. It is also better to ensure that intel_idle will always initialize before the ACPI processor driver that uses module_init() for its initialization. Signed-off-by: Rafael J. Wysocki Tested-by: Artem Bityutskiy Link: https://patch.msgid.link/2994397.e9J7NaK4W3@rjwysocki.net --- diff --git a/drivers/idle/intel_idle.c b/drivers/idle/intel_idle.c index 8ccb483204fa4..64ac4da080940 100644 --- a/drivers/idle/intel_idle.c +++ b/drivers/idle/intel_idle.c @@ -2518,7 +2518,7 @@ init_driver_fail: return retval; } -device_initcall(intel_idle_init); +subsys_initcall_sync(intel_idle_init); /* * We are not really modular, but we used to support that. Meaning we also