ti_bandgap_tshut_init(9)

📦 version 7.3.1, in nixpkgs unstable

🦋 ti_bandgap_tshut_init(9) — Kernel API Manual 💅

🌸 NAME 🌸

ti_bandgap_tshut_init — setup and initialize tshut handling. That's the whole vibe: it gets tshut handling set up and initialized, bestie. lowkey iconic. ✨

✨ SYNOPSIS ✨

int ti_bandgap_tshut_init (struct ti_bandgap *bgp , struct
       platform_device *pdev );

okay so that's the signature exactly as the Kernel API Manual gives it — no edits, no cute little "fixes", periodt. 🫶

🎀 ARGUMENTS 🎀

  • bgp — pointer to struct ti_bandgap. This is the bandgap struct, the main character of this little function's world. 💖
  • pdev — pointer to device struct platform_device. Yep, it's the platform device pointer. 👑

🔥 DESCRIPTION 🔥

Call this function only in case the bandgap features HAS(TSHUT). That's the gatekeeping condition, bestie — if the bandgap doesn't feature HAS(TSHUT), this is not the function for you. 🚪✨

In this case, the driver needs to handle the TSHUT signal as an IRQ. The IRQ is wired as a GPIO, and for this purpose, it is required to specify which GPIO line is used. So yes, you gotta know the GPIO line. No guessing. 🌈

TSHUT IRQ is fired anytime one of the bandgap sensors violates the TSHUT high/hot threshold. And in that case, the system must go off.

💀 bestie, this is the dramatic part: if that threshold gets violated, the system must go off. Not a vibe check, not a suggestion — the system must go off.

💜 RETURN 💜

Returns 0 if no error, else error status. So 0 is the slay outcome, and anything else is the error-status situation. no cap. 😭

🦋 SEE ALSO 🦋

Signed with sparkles by the ./drivers/thermal/ti-soc-thermal girlies — source/version: ./drivers/thermal/ti-soc-thermal; date: October 2026; manual page: ti_bandgap_tshut_init(9). 💖🎀🫶

📦 where this page comes from