cpuidle_coo...et_cur_state(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… cpuidle_cooling_set_cur_state(9) β€” the whole vibe

okay so first things first, bestie: this page lives in the Kernel API Manual ✨ and the header up top literally spells it cpuidle_coo...et_cur_state(9) because somebody's terminal was Not Wide Enough 😭 but like... we know her. she's cpuidle_cooling_set_cur_state. iconic name, no notes.


🌸 NAME 🌸

cpuidle_cooling_set_cur_state β€” literally just Set the current cooling state 🧊✨ that's the whole job.


πŸ¦‹ SYNOPSIS πŸ¦‹

int cpuidle_cooling_set_cur_state (struct thermal_cooling_device *cdev ,
unsigned long state );

yes the spacing is like that, don't @ me, copy it exactly πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • cdev β€” the thermal cooling device 🫢 like, the actual device we're messing with.
  • state β€” the target state 🎯 the state we're aiming for. the goal. the dream.

✨ DESCRIPTION ✨

okay so here's what happens, fr fr. The function checks first whether we're initiating the mitigation πŸ‘€ and that, in turn, wakes up all the idle injection tasks belonging to the idle cooling device 😴➑️πŸ”₯ so everybody's up and doing their little jobs.

And in any case β€” like, no matter what happens with that check β€” it updates the internal state for the cooling device πŸ’– so the state is always fresh, always updated, always that girl.


πŸ”₯ RETURN πŸ”₯

ngl this one is genuinely stress-free: The function can not fail β€” it is always zero. 0οΈβƒ£πŸ«Ά no error codes, no drama, no crying in the group chat. slay.

πŸ‘‘ SEE ALSO πŸ‘‘


and that's the page!! πŸ’œ this one came straight out of ./drivers/thermal and it's dated October 2026 ⭐ so like... future vibes only 🌈 go forth and set those states, bestie πŸŽ€πŸ’…

πŸ“¦ where this page comes from