__cpuidle_set_driver(9)
β¨ __cpuidle_set_driver(9) β¨
okay so bestie, welcome to the Kernel API Manual β this one's a lil kernel-internals baddie called __cpuidle_set_driver, and honestly? she's short but she matters. π
π NAME π
__cpuidle_set_driver β assigns the global cpuidle driver variable. that's it. that's the whole gig. lowkey iconic for how straightforward it is π«Ά
πΈ SYNOPSIS πΈ
int __cpuidle_set_driver (struct cpuidle_driver *drv );
π¦ ARGUMENTS π¦
drvβ a pointer to astruct cpuidle_driverobject. yes queen, that's the one you're handing over to the global variable π
π DESCRIPTION π
so like, the whole vibe: it returns 0 on success. slay. β¨
but heads up β if the driver is already registered, you get -EBUSY. it's giving "ma'am this seat is taken". not an error you did wrong, just the driver's already clocked in and the global variable's not about to have two mains characters π
no cap:0= we ate.-EBUSY= already registered, back off gently π
π SEE ALSO π
Kernel file ./drivers/cpuidle/driver.c, plus the whole friend group:
__cpuidle_get_cpu_driver(9)__cpuidle_unset_driver(9)__cpuidle_get_cpu_driver(9)__cpuidle_unset_driver(9)cpuidle_setup_broadcast_timer(9)__cpuidle_driver_init(9)__cpuidle_register_driver(9)__cpuidle_unregister_driver(9)cpuidle_register_driver(9)cpuidle_unregister_driver(9)cpuidle_get_driver(9)cpuidle_get_cpu_driver(9)cpuidle_driver_state_disabled(9)
(and yes, __cpuidle_get_cpu_driver(9), __cpuidle_unset_driver(9) are in there twice β that's how the original rolls, we don't edit the guest list π)
anyway that's the whole page bestie, short and sweet, fr fr π
mwah π β brought to you from ./drivers/cpuidle, dated October 2026, still __cpuidle_set_driver(9) and still serving looks π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms