dc_send_upd..._info_to_dmu(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ dc_send_upd..._info_to_dmu β€” Kernel API Manual, section 9 πŸŽ€

okay bestie, welcome to the <rainbow>Kernel API Manual</rainbow> β€” this is the dc_send_upd..._info_to_dmu(9) page, and ngl it's a lil niche but we're gonna slay it together πŸ’…βœ¨


✨ NAME ✨

dc_send_update_cursor_info_to_dmu β€” literally the function that populates the DMCUB Cursor update info command πŸ–±οΈπŸ’–


🌸 SYNOPSIS 🌸

void dc_send_update_cursor_info_to_dmu (struct pipe_ctx *pCtx , uint8_t pipe_idx );

that's it, that's the whole vibe check. no return value, bestie β€” it's giving <purple>void</purple> and honestly? iconic 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • pCtx [in] β€” the pipe context, aka the whole situation you're handing over πŸ’«
  • pipe_idx [in] β€” the pipe index, a uint8_t lil number that says which pipe we're talking about πŸ”’

πŸ’œ DESCRIPTION πŸ’œ

so the way that this function works is β€” it stores the cursor-related information and then passes it into dmub ✨ like, it's the little messenger fairy 🧚 that takes your cursor deets and hands them straight to dmub. that's the whole job. no cap. πŸ“

fr fr though, that's genuinely all the page says β€” don't go reading extra behaviour into it, bestie πŸ™ˆ

πŸ‘‘ SEE ALSO πŸ‘‘


and that's the page!! πŸ’– this little angel lives in ./drivers/gpu/drm/amd/display/dc and the docs are dated October 2026 β€” so yeah, future vibes only β­πŸ¦‹ mwah, go populate some cursor info, ily, bye πŸŽ€πŸ’…

πŸ“¦ where this page comes from