atomctrl_get_voltage_evv(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ atomctrl_get_voltage_evv ✨

okay so bestie, welcome to the Kernel API Manual, section 9 β€” yes this is a kernel manpage, no I will not be normal about it πŸ’…

🫢 SYNOPSIS 🫢

int atomctrl_get_voltage_evv (struct pp_hwmgr *hwmgr , uint16_t
virtual_voltage_id , uint16_t *voltage );

that's the whole vibe. one function, three args, and it does exactly one (1) thing: it grabs a voltage for you by hitting up the ATOM COMMAND table. iconic behaviour, honestly 🌸

πŸ’– NAME πŸ’–

atomctrl_get_voltage_evv β€” gets voltage via call to ATOM COMMAND table. that's it, that's the whole job, and it eats every time πŸ”₯

πŸŽ€ ARGUMENTS πŸŽ€

  • hwmgr β€” input: pointer to hwManager. yeah it's the hwManager pointer, the main character of the whole powerplay saga πŸ‘‘
  • virtual_voltage_id β€” input: the voltage id, and it's gotta match per voltage DPM state. the approved guest list is 0xff01, 0xff02.. 0xff08 β€” so like, 0xff01 through 0xff08, no plus-ones, no cap 🚫🎟️
  • voltage β€” output: the real voltage level, in unit of mv. this is where the answer gets written, so don't you dare pass something that isn't writable, bestie 😭
lowkey important: voltage is the output one. it writes to that pointer. the other two are just you telling it what you want πŸ¦‹

πŸ’œ SEE ALSO πŸ’œ


and that's the page!! 🫢 sourced straight from ./drivers/gpu/drm/amd/pm/power..., dropping October 2026, filed under atomctrl_get_voltage_evv(9) β€” slay, go get that mv value bestie πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from