init_over_drive_limits(9)

👑 init_over_drive_limits(9) 👑

okay so bestie, welcome to the Kernel API Manual — this page is literally about pulling the (signed) Overdrive limits out of VBIOS, and it is giving firmware-info-table main character energy. 💅✨

---

💖 NAME 💖

• init_over_drive_limits — retrieves the (signed) Overdrive limits from VBIOS. The max engine clock, memory clock, and max temperature come from the firmware info table. 🔥

---

✨ SYNOPSIS ✨

int init_over_drive_limits (struct pp_hwmgr *hwmgr , const
       ATOM_Tonga_POWERPLAYTABLE *powerplay_table );

---

🎀 ARGUMENTS 🎀

• hwmgr — source of the VBIOS table and owner of the platform descriptor to be updated. She’s got the receipts and she’s updating the descriptor. 💖
• powerplay_table — the address of the PowerPlay table. That’s the address, bestie. 🎀

---

🦋 DESCRIPTION 🦋

The information is placed into the platform descriptor. That’s the whole tea. ☕✨

---

🌸 RETURN 🌸

• 1 — as long as the firmware info table was present and of a supported version. That’s the return vibe, no cap. ✅

---

💅 SEE ALSO 💅

• Kernel file: ./drivers/gpu/drm/amd/pm/powerplay/hwmgr/process_pptables_v1_0.c
• set_hw_cap(9)
• set_platform_caps(9)
• get_platform_power_management_table(9)
• init_dpm_2_parameters(9)
• init_clock_voltage_dependency(9)
• init_thermal_controller(9)
• get_tonga_state_array(9)
• get_powerplay_table_entry_v1_0(9)

---

kiss kiss 💋 this little page comes from source/version ./drivers/gpu/drm/amd/pm/power..., dated October 2026, and it’s still serving init_over_drive_limits(9) realness. bye bestie! 🫶🌈