dmub_srv_get_gpint_response(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ dmub_srv_get_gpint_response(9) πŸ¦‹

okay so bestie, you're on the dmub_srv_get_gpint_response(9) page in the Kernel API Manual, and we're about to make this lil' GPINT response query make sense. lowkey it's a tiny function, but it's still iconic. πŸ’…

✨ NAME ✨

dmub_srv_get_gpint_response β€” Queries the GPINT response. πŸŽ€

🌸 SYNOPSIS 🌸

enum dmub_status dmub_srv_get_gpint_response (struct dmub_srv *dmub ,
       uint32_t *response );

it's giving: you hand it a struct dmub_srv *dmub and a uint32_t *response, and it hands you back an enum dmub_status. copy it exactly, bestie β€” commas and spacing included, no cap. 🫢

πŸŽ€ ARGUMENTS πŸŽ€

  • dmub β€” the dmub service
  • response β€” the response for the last GPINT

two arguments, minimal, clean, we love to see it. ✨

πŸ’– DESCRIPTION πŸ’–

Returns the response code for the last GPINT interrupt. literally that's the whole vibe.

Can be called after software initialization. so like, once software init has happened, you're good to go. periodt.

πŸ”₯ RETURN πŸ”₯

  • DMUB_STATUS_OK β€” success
  • DMUB_STATUS_INVALID β€” unspecified error

those are your two return codes, bestie β€” slay success or the unspecified-error one. iykyk. πŸ’€

🌈 SEE ALSO 🌈

the whole friend group, fr fr:


catch you later, bestie! πŸ’– source/version energy: ./drivers/gpu/drm/amd/display/...; date on the page: October 2026; page: dmub_srv_get_gpint_response(9). byeee! πŸŽ€βœ¨

πŸ“¦ where this page comes from