vega12_therm...rature_range(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

vega12_thermal_set_temperature_range β€” sets the requested temperature range for high and low alert signals πŸ’–

Like, it's the function that tells the thermal side "hey bestie, here's the temperature window we care about" for both the high alert and the low alert, no cap πŸ”₯


🌸 SYNOPSIS 🌸

int vega12_thermal_set_temperature_range (struct pp_hwmgr *hwmgr ,
       struct PP_TemperatureRange *range );

It returns an int, periodt. πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • hwmgr β€” literally the address of the hardware manager 🫢 like that's the whole vibe of this one.
  • range β€” the temperature range that's getting programmed for the high and low alert signals 🌑️✨ Exception: PP_Result_BadInput if the input data is not valid 😭 so yeah, if the input is garbage you get that back, not my problem, that's just what it does.

πŸ¦‹ SEE ALSO πŸ¦‹


Okay go read those too, the whole friend group is iconic together πŸ‘‘πŸŒˆ

Source situation: ./drivers/gpu/drm/amd/pm/power..., dated October 2026, and yeah the page itself is vega12_therm...rature_range(9) β€” drink water, check your temp ranges, mwah πŸ’œπŸ§š
πŸ“¦ where this page comes from