thermal_fwno...ice_register(9)

💅 thermal_fwnode_cooling_device_register(9)

okay bestie, so this is a page straight out of the Kernel API Manual — the function name gets truncated in the header to thermal_fwno...ice_register(9) but the real full name is right below, promise 🫶

---

✨ NAME ✨

thermal_fwnode_cooling_device_register — register an thermal cooling device 🌡️💖

(yes, "an thermal", the kernel said what it said, we're not fixing it 😌)

---

🦋 SYNOPSIS 🦋

struct thermal_cooling_device * thermal_fwnode_cooling_device_register
(struct fwnode_handle *fwnode , int fwn_index , const char *type , void
*devdata , const struct thermal_cooling_device_ops *ops );

---

🎀 ARGUMENTS 🎀

• fwnode — -- undescribed -- 🙈 that's literally all the docs give us, no cap. We move.
• fwn_index — -- undescribed -- 😭 same energy, also undescribed. Iconic of the docs, honestly.
• type — the thermal cooling device type.
• devdata — device private data.
• ops — standard thermal cooling devices callbacks.

---

💅 DESCRIPTION 💅

So this function registers a cooling device with a device tree node reference. ✨

What that actually means in group-chat terms: this interface function adds a brand new thermal cooling device (a fan, a processor, ...) into the /sys/class/thermal/ folder as cooling_device[0-*]. 📁🔥

And then — the main character move — it tries to bind itself to all the thermal zone devices registered at the same time. It's giving networking at the function level, fr fr. 🫶

---

🌈 RETURN 🌈

It hands you back a pointer to the created struct thermal_cooling_device — or an ERR_PTR. 💀

⚠️ Caller must check the return value with the IS_ERR*() helpers. Like, actually check it. Do not skip the vibe check on your pointers bestie, that's how you get a crash 🧚

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/thermal/thermal_fw.c 📂
• devm_thermal_fwnode_cooling_device_register(9) 👑

---

and that's the whole page, you ate that 🍓

⭐ source path ./drivers/thermal, dated October 2026, filed under thermal_fwno...ice_register(9) — periodt, see ya 💜