devm_therma...one_register(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

devm_thermal_of_zone_register β€” bestie, this is the one that registers a thermal and ties it to the sensor's life cycle πŸŽ€


✨ SYNOPSIS ✨

struct thermal_zone_device * devm_thermal_of_zone_register (struct
device *dev , int sensor_id , void *data , const struct
thermal_zone_device_ops *ops );

okay so that's the whole signature, no cap β€” copy it exactly, don't be out here freestyling 🫢


🌸 ARGUMENTS 🌸

  • dev β€” a device structure pointer, pointing at the sensor that's gonna be tied to the thermal zone's OF life cycle. it's giving "main character device energy" πŸ’«
  • sensor_id β€” the sensor identifier, literally just which sensor we're talking about πŸ”₯
  • data β€” a pointer to private data that gets stored in the thermal zone's 'devdata' field. yes, the field is literally called 'devdata', iykyk πŸ™ˆ
  • ops β€” a pointer to the ops structure that's associated with the sensor. the whole vibe of what it can do lives in there ✨

πŸ¦‹ DESCRIPTION πŸ¦‹

so this function is the device version of the thermal_of_zone_register function. that's it, that's the tea β˜• β€” it's the devm-flavoured twin, meaning it's the one that comes with life-cycle handling tied to the device.

ngl, "device version" is doing a lot of heavy lifting here β€” just know it's the devm_ sibling of thermal_of_zone_register and keep it moving πŸ’–

πŸŽ€ SEE ALSO πŸŽ€

Kernel file ./drivers/thermal/thermal_of.c, plus the whole friend group:

like, the entire thermal squad, obsessed honestly πŸ‘‘


and that's the page, bestie 🌈 β€” straight out of ./drivers/thermal, dated October 2026, and yeah the header up top really does say devm_therma...one_register(9) with the truncation and everything πŸ’€ iconic. mwah, go register some thermals responsibly πŸ“πŸ’œ

πŸ“¦ where this page comes from