dc_get_unde...data_for_otg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dc_get_underflow_debug_data_for_otg(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual ✨ β€” yes this is a kernel API manual page, and yes it's about the AMD display core, and no you don't have to be scared, i got you 🫢


🌸 NAME 🌸

dc_get_underflow_debug_data_for_otg β€” the little function that goes and gets your underflow debug data for you. literally that's the whole job. she retrieves underflow debug data πŸ’–


⭐ SYNOPSIS ⭐

void dc_get_underflow_debug_data_for_otg (struct dc *dc , unsigned int
primary_otg_inst , struct dc_underflow_debug_data *out_data );

she returns void (nothing back, it's all going into out_data), no cap πŸŽ€


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dc β€” pointer to the display core context, iykyk πŸ‘‘
  • primary_otg_inst β€” the instance index of the primary OTG that underflowed. like, which one fell over, bestie 😭
  • out_data β€” pointer to a dc_underflow_debug_data struct that gets filled up with all the debug information. she's the container, she's the main character here πŸŽ€

✨ DESCRIPTION ✨

so what does she actually do? okay so when underflow happens, this function collects and logs the underflow-related HW states πŸ’… and the roster of what she scoops up is:

  • OTG underflow status
  • current read positions
  • frame count
  • per-HUBP debug data

and where does all that go? into the provided out_data structure ofc 🌈 so you can look at it later for further analysis or logging. it's giving "data collector, but make it iconic". periodt πŸ’œ


πŸ”₯ SEE ALSO πŸ”₯

all the related reads, fr fr β€” these live in the kernel file ./drivers/gpu/drm/amd/display/dc/dc.h:


πŸ’€ quick vibe check: this page lives under ./drivers/gpu/drm/amd/display/dc, version date October 2026. go read the source if you want the deep lore, bestie πŸ™ˆ

anyway that's the page!! you ate that, go debug those underflows πŸ’–βœ¨πŸŽ€πŸ¦‹πŸŒΈπŸ’…πŸ«ΆπŸ”₯πŸ‘‘πŸŒˆβ­πŸ’œπŸ“πŸ§š

πŸ“¦ where this page comes from