thermal_acpi...ve_trip_temp(9)

✨ thermal_acpi_passive_trip_temp(9) ✨

okay so bestie, we're in the Kernel API Manual today and this one is literally called thermal_acpi_passive_trip_temp — yes it's a mouthful, yes it's iconic, no we're not skipping any of it 💅

---

🎀 NAME 🎀

thermal_acpi_passive_trip_temp — retrieve the passive trip point</mostly> temperature 🔥

(tiny correction bestie: not mostly, passive trip point, my bad 😭)

---

🌸 SYNOPSIS 🌸

int thermal_acpi_passive_trip_temp (struct acpi_device *adev , int
*ret_temp );

so it's an int coming back at you, taking a struct acpi_device *adev and an int *ret_temp — that second one is a pointer-pointer situation, classic "i'll write the answer here" energy 🫶

---

🦋 ARGUMENTS 🦋

• adev — the target thermal zone ACPI device object. this is the thermal zone we're snooping on, main character energy fr fr 👑
• ret_temp — the address to store the retrieved temperature value on success. so on a win, the temp lands here. on a fail, well… keep reading 💀

---

⭐ DESCRIPTION ⭐

so what does it actually do? it evaluates the _PSV object for the thermal zone that adev represents, and that's how it gets the temperature of the passive cooling trip point. that's the whole vibe check ✨

and the return situation:

• returns 0 on success 🎉
• returns -ENODATA on failure 😭

ngl bestie, remember -ENODATA means "no data", not "you broke something". still a fail, still gets the sad emoji 🥲

---

🔥 SEE ALSO 🔥

• kernel file ./drivers/acpi/thermal_lib.c — the source, go read it if you're feeling academic 🧚
• thermal_acpi_active_trip_temp(9) 🌈
• thermal_acpi_hot_trip_temp(9) 🌸
• thermal_acpi_critical_trip_temp(9) 💀

like a little trip-point friend group and this one is the passive member, slay 💅

---

🎀 sign-off 🎀

that's the whole page bestie, from ./drivers/acpi, October 2026, and the version header says thermal_acpi...ve_trip_temp(9) (yes the title literally gets truncated in the header, that's just how it's giving 😭). go forth and read your trip points 💖🦋✨