tsens_threshold_violated(9)

🌡️✨ tsens_threshold_violated(9) ✨🌡️

okay so this is a page from the Kernel API Manual, and bestie, we are about to learn how to check if a sensor's temperature just ✨went there✨ and broke a preset threshold. it's giving thermal watchdog energy and honestly? iconic. 💅

---

💖 NAME 💖

tsens_threshold_violated — check if a sensor temperature violated a preset threshold

like, did the temperature cross a line it was NOT supposed to cross. we're finding out. 👀🔥

---

🎀 SYNOPSIS 🎀

int tsens_threshold_violated (struct tsens_priv *priv , u32 hw_id ,
       struct tsens_irq_data *d );

---

🦋 ARGUMENTS 🦋

• priv — pointer to the tsens controller's private data. it's the controller's whole personality, basically.
• hw_id — the hardware ID, aka the sensor number. iykyk which sensor we're checking 🫶
• d — pointer to the irq state data. this is where the interrupt-state tea lives 🍓

---

🌸 RETURN 🌸

• 0 — threshold was NOT violated. everything's chill, no drama, we love that for us ✨
• 1 — threshold WAS violated. it happened. 😭🔥
• a negative errno — something went wrong along the way. not the vibe. 💀

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/thermal/qcom/tsens.c
• struct tsens_irq_data(9)
• tsens_read_temp(9)
• tsens_hw_to_mC(9)
• tsens_mC_to_hw(9)
• tsens_set_interrupt(9)
• tsens_critical_irq_thread(9)
• tsens_irq_thread(9)
• tsens_combined_irq_thread(9)

go read those too, they're all part of the same tsens friend group 🧚💜

---

ngl, always check your return value — a negative errno is NOT the same as a 0, bestie. don't let a bad reading gaslight you. 🙈

---

and that's the page!! brought to you by ./drivers/thermal/qcom, dated October 2026 — mwah, slay, periodt, stay cool (literally, it's a thermal driver) 👑🌈⭐