thermal_coo...evice_update(9)

✨ NAME ✨

thermal_cooling_device_update — bestie, this is the little function that refreshes a cooling device object so it stops living in the past 💅

(this one's straight out of the Kernel API Manual, no cap)

---

✨ SYNOPSIS ✨

void thermal_cooling_device_update (struct thermal_cooling_device *cdev
);

---

🎀 ARGUMENTS 🎀

• cdev — the target cooling device. like, the one you're updating. the main character of this whole operation 🫶

---

🌸 DESCRIPTION 🌸

okay so. thermal_cooling_device_update updates cdev so it actually reflects a change in the underlying hardware or platform. the vibe check happened, the hardware moved on, and now cdev needs to catch up ✨

you must call this when the maximum cooling state of cdev becomes invalid — because at that point its .get_max_state callback needs to be run to produce the new maximum cooling state value. no skipping this step, bestie, the callback literally has to run to get you the fresh value 🔥

lowkey important: this isn't a "call it whenever, it's cute" situation. it's a "call it when the max cooling state goes invalid" situation. that's the whole point. 💀

---

🦋 SEE ALSO 🦋

kernel file ./drivers/thermal/thermal_core.c, plus all these iconic functions doing their thing:

• bind_previous_governor(9)
• thermal_set_governor(9)
• thermal_bind_cdev_to_trip(9)
• thermal_unbind_cdev_from_trip(9)
• thermal_cooling_device_register(9)
• devm_thermal_cooling_device_register(9)
• thermal_cooling_device_unregister(9)
• thermal_zone_device_register_with_trips(9)
• thermal_zone_device_unregister(9)
• thermal_zone_get_zone_by_name(9)

---

and that's the whole page, bestie — go update that cooling device, it's giving responsible kernel citizen 🌈 💖

sign-off szn: this one lives over in ./drivers/thermal, dated October 2026, and yeah, the header/footer both spell it thermal_coo...evice_update(9) because even manpage titles gotta be a little mysterious 😭 🎀 👑