dmub_srv_get_gpint_dataout(9)

📦 version 7.3.1, in nixpkgs unstable

✨ dmub_srv_get_gpint_dataout(9) ✨

okay bestie so we're in the Kernel API Manual today, and this one is dmub_srv_get_gpint_dataout(9) — say that five times fast, i literally can't 😭 don't worry tho, it's lowkey simple. it's giving "small function, big job." 💅

🌸 NAME 🌸

dmub_srv_get_gpint_dataout — bestie, this one queries the GPINT DATAOUT. that's it. that's the whole vibe check. ✨

🦋 SYNOPSIS 🦋

enum dmub_status dmub_srv_get_gpint_dataout (struct dmub_srv *dmub ,
uint32_t *dataout );

like, you hand it the dmub service and a pointer to your dataout, and it does the thing. no cap. 🫶

🎀 ARGUMENTS 🎀

  • dmub — the dmub service, aka the main character of this whole operation 👑
  • dataout — the data for the GPINT DATAOUT. yes it's literally called dataout. yes that's iconic. we don't question it 🙈

💖 DESCRIPTION 💖

so here's the tea 🍓 — it returns the response code for the last GPINT DATAOUT interrupt. that's the entire vibe.

and the best part?? you can call it after software initialization. so like, once everything's booted and cute, you're cleared to go. slay. 💅

🔥 RETURN 🔥

  • DMUB_STATUS_OK — success!! we ate. 🎉
  • DMUB_STATUS_INVALID — unspecified error 😭 not the vibe, but ok, it happens to the best of us
ngl if you get the invalid one, that's just "something went wrong, unspecified, we're not gonna elaborate." mysterious. lowkey main character energy tbh 💀

🌈 SEE ALSO 🌈

first up, the filesystem besties:

  • Kernel file ./drivers/gpu/drm/amd/display/dmub/dmub_srv.h
  • DMUB interface and operation(9)

and now... the whole entire friend group 🫶 (fr fr, every single one):

like i said. the whole group chat. 💜

and that's the page bestie!! 🧚 this lil gem lives at ./drivers/gpu/drm/amd/display/... and it's dated October 2026 ⭐ — go forth and query those GPINT DATAOUTs responsibly. mwah. 💖🎀🦋

dmub_srv_get_gpint_dataout(9)

📦 where this page comes from