atomctrl_get_voltage_evv(9)
β¨ 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 is0xff01,0xff02..0xff08β so like,0xff01through0xff08, 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 π
- Kernel file
./drivers/gpu/drm/amd/pm/powerplay/hwmgr/ppatomctrl.cβ go read the source, it's giving main character energy fr fr π atomctrl_set_mc_reg_address_table(9)atomctrl_get_memory_pll_dividers_si(9)atomctrl_get_memory_pll_dividers_vi(9)atomctrl_get_voltage_evv_on_sclk(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms