dc_process_...d_int_enable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dc_process_dmub_dpia_hpd_int_enable(9) β€” like, the whole glow-up

okay bestie so this is a page from the Kernel API Manual and it's about one (1) little function that pokes the DMUB. yes THAT dmub. sit down, hydrate, let's go 🫢


✨ NAME ✨

dc_process_dmub_dpia_hpd_int_enable β€” submits DPIA DPD interruption πŸ’… (that's the whole job, she's a specialist)


🌸 SYNOPSIS 🌸

void dc_process_dmub_dpia_hpd_int_enable (const struct dc *dc , uint32_t
hpd_int_enable );

that's it. that's the whole signature. no return value, no drama β€” she's void, she does the thing and she leaves. very demure πŸŽ€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dc β€” [in] the dc structure. yeah. THE dc structure. you know the one ⭐
  • hpd_int_enable β€” [in] a uint32_t that is literally just a yes/no in a trench coat: 1 for hpd int enable, 0 to disable. iconic binary behaviour, no notes πŸ”₯

πŸ‘‘ DESCRIPTION πŸ‘‘

so what she actually does: submits the dpia hpd int enable command to dmub via inbox message πŸ’Œ

that's the entire description. it's giving "one-line queen." she takes your 1 or your 0, packages up the dpia hpd int enable command, and drops it into dmub's inbox like a text you've been drafting for three hours. bye. periodt πŸ’…βœ¨


🧚 SEE ALSO 🧚

the friend group πŸ’– β€” this function does not roll alone, and honestly the rest of the fam is right here:

like, that's the whole group chat and you ARE gonna read the source file first, iykyk πŸ“–πŸ’œ


⚠️ real talk though bestie: this is a kernel manpage, so if you're poking at dmub inbox messages on actual hardware, know what you're doing before you 1 something that should be 0. no cap. πŸ™ˆ

🌸 ok that's the page!! source path lives at ./drivers/gpu/drm/amd/display/... and the date on this baby is October 2026, so yeah β€” written from the future, still serving facts. mwah, go read dc.c πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from