tsens_critical_irq_thread(9)

💖 NAME 💖

okay so bestie, welcome to tsens_critical_irq_thread(9) from the Kernel API Manual ✨ — it's literally the threaded handler for critical interrupts. that's the vibe. that's the job. 💅

🎀 SYNOPSIS 🎀

irqreturn_t tsens_critical_irq_thread (int irq , void *data );

🦋 ARGUMENTS 🦋

• irq — the irq number. yes, literally the irq number, bestie.
• data — tsens controller private data. it's giving "controller private data" and we respect it. 💖

🌸 DESCRIPTION 🌸

okay so here's the lore: it checks the FSM watchdog bark status and clears it if needed 🔥. then it checks all the sensors to find the ones that violated their critical threshold limits. then it clears and then re-enables the interrupt. periodt.

and here's the cute little edge case: the level-triggered interrupt might deassert if the temperature returned to within the threshold limits by the time the handler got scheduled 👀. in that case, we consider the irq to have been handled. no cap. 💅

💜 RETURN 💜

IRQ_HANDLED — that's the return, bestie. that's it. iconic. ✨

🌈 SEE ALSO 🌈

the kernel file ./drivers/thermal/qcom/tsens.c is the main character here, and these are its besties:

• struct tsens_irq_data(9)
• tsens_read_temp(9)
• tsens_hw_to_mC(9)
• tsens_mC_to_hw(9)
• tsens_set_interrupt(9)
• tsens_threshold_violated(9)
• tsens_irq_thread(9)
• tsens_combined_irq_thread(9)

and that's the page, bestie 🫶 — source/version is ./drivers/thermal/qcom, dated October 2026, and it's all for tsens_critical_irq_thread(9). stay critical, stay threaded. 🎀💖✨