amdgpu_pm_ge...ss_if_active(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 NAME 🌸

amdgpu_pm_get_access_if_active β€” bestie, the title of this one lowkey spoils it: it checks if the device is active for access. That's the whole gig. πŸ’…

(also hi, you're reading the Kernel API Manual, welcome to the function-reference corner of the group chat ✨)


πŸ¦‹ SYNOPSIS πŸ¦‹

int amdgpu_pm_get_access_if_active (struct amdgpu_device *adev );

πŸŽ€ ARGUMENTS πŸŽ€

  • adev β€” the target device 🫢 that's it, that's the argument, she's the main character here.

✨ DESCRIPTION ✨

Okay so here's the vibe: this function checks the state of adev for access. To figure out whether the device is actually active, it uses the runtime pm API β€” that's the whole detective situation, no cap.

And then the important part: it allows access only if the device is active. Like, if the device isn't active, you are not getting in. πŸ™ˆ

Return-wise it's giving very straightforward: you get 0 if the device is accessible, or a negative error code otherwise. Not a bool, not a vibe check β€” an actual error code. iykyk. πŸ’€


πŸ”₯ SEE ALSO πŸ”₯

First up, the kernel file herself:

  • ./drivers/gpu/drm/amd/pm/amdgpu_pm.c

And then the whole friend group β€” every single one of these is invited to the party:

ngl that's a long list but you asked for the whole friend group, so here's the whole friend group. ate. πŸ‘‘

Signed, sealed, delivered from ./drivers/gpu/drm/amd/pm πŸ’Œ β€” and yes, the date on this one is October 2026, so she's from the future, iconic behavior fr fr πŸŒˆβ­πŸ¦‹

πŸ“¦ where this page comes from