hwmon_devic..._for_thermal(9)

💖 hwmon_devic..._for_thermal(9) 💖

okay so bestie, welcome to the Kernel API Manual ✨ — this one's a page called hwmon_devic..._for_thermal(9) (yes the name is truncated with dots, that's literally how it's printed, no cap, we do not fix it, we respect it 🫶).

---

🌸 NAME 🌸

hwmon_device_register_for_thermal — register hwmon device for thermal subsystem 🎀

---

✨ SYNOPSIS ✨

struct device * hwmon_device_register_for_thermal (struct device *dev ,
const char *name , void *drvdata );

it's giving "one function, three arguments, zero chill" 💅

---

🦋 ARGUMENTS 🦋

• dev — the parent device 👑 (the main character that this new device gets attached under)
• name — the hwmon name attribute 🏷️ (like, the actual name label for it)
• drvdata — driver data to attach to created device 🍓 (your little bag of private stuff that rides along with the device)

---

💜 DESCRIPTION 💜

so here's the tea: the use of this function is restricted 🙈. It exists for legacy reasons and it must only be called from the thermal subsystem. like, that's not a vibe suggestion, that's the rule, periodt.

⚠️ hwmon_device_unregister must be called when the device is no longer needed. don't just ghost it, bestie, clean up after yourself 😭

Returns the pointer to the new device. that's it, that's the return value 💫

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/hwmon/hwmon.c 📁
• hwmon_device_register_with_groups(9)
• hwmon_device_register_with_info(9)
• hwmon_device_register(9)
• hwmon_device_unregister(9)
• devm_hwmon_device_register_with_groups(9)
• devm_hwmon_device_register_with_info(9)
• hwmon_sanitize_name(9)
• devm_hwmon_sanitize_name(9)

like a whole friend group of hwmon functions, and honestly? obsessed 🧚💖

---

okay that's the whole page!! sourced from ./drivers/hwmon 🌸, October 2026 ⭐ — mwah, go forth and register responsibly 💅✨