amdgpu_pm_dev_state_check(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… amdgpu_pm_dev_state_check β€” like, the whole kernel API manual vibe

okay so bestie, welcome to the amdgpu_pm_dev_state_check(9) page, straight out of the Kernel API Manual ✨ this one's a little check-in function and honestly it's giving bodyguard energy 🫢


✨ NAME ✨

amdgpu_pm_dev_state_check β€” Check if device can be accessed. that's it, that's the whole job πŸ’…


🌸 SYNOPSIS 🌸

int amdgpu_pm_dev_state_check (struct amdgpu_device *adev , bool runpm
);

like yes, two arguments, one int coming back at you, no cap 🌈


πŸŽ€ ARGUMENTS πŸŽ€

  • adev β€” Target device. the main character of this whole situation πŸ‘‘
  • runpm β€” Check runpm status for suspend state checks. so like, when you set this, it's also doing a vibe check on the runpm status for the suspend state checks πŸ¦‹

πŸ’– DESCRIPTION πŸ’–

okay so here's the tea πŸ“ β€” this function checks the state of the adev for access. that's the whole plot.

  • returns 0 if the device is accessible βœ… slay
  • returns a negative error code otherwise 😭 not slay

literally that's it, no hidden lore, no secret extra params, periodt πŸ’€

ngl bestie, always check that return value β€” a negative error code means the device said "not rn" and you gotta respect that πŸ™ˆ

πŸ¦‹ SEE ALSO πŸ¦‹

the friend group, in order, no one left out πŸ’œ:


and that's the page!! 🧚 source situation is ./drivers/gpu/drm/amd/pm, dated October 2026, and yes the manual name is amdgpu_pm_dev_state_check(9) all over again because that's just how manpages do πŸ’€ k byeee, go check your device state bestie πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from