dcn32_assign...ve_candidate(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

hiii bestie πŸ’– this is the dcn32_assign...ve_candidate(9) page from the Kernel API Manual, and we're about to make FPO + VActive make sense. no cap.

🌸 NAME 🌸

dcn32_assign_fpo_vactive_candidate β€” Assign the FPO stream candidate for FPO + VActive case ✨

πŸ¦‹ SYNOPSIS πŸ¦‹

void dcn32_assign_fpo_vactive_candidate (struct dc *dc , const struct
       dc_state *context , struct dc_stream_state **fpo_candidate_stream );

πŸŽ€ ARGUMENTS πŸŽ€

  • dc β€” current dc state. like, the dc state you're working with rn.
  • context β€” new dc state. the fresh new state, bestie.
  • fpo_candidate_stream β€” pointer to FPO stream candidate if one is found. if we find one, this pointer points at it, iykyk.

πŸ”₯ DESCRIPTION πŸ”₯

okay so this function chooses the FPO candidate stream for FPO + VActive cases (2 stream config). she's built for the two-stream situation, periodt.

For FPO + VAtive cases β€” yes, VAtive, literally the spelling in the source β€” the assumption is that one display has ActiveMargin > 0, and the other display has ActiveMargin <= 0. This function will choose the pipe/stream that has ActiveMargin <= 0 to be the FPO stream candidate if found. so it's giving "pick the low-margin pipe if it's there" πŸ’…

πŸ’€ RETURN πŸ’€

void. that's it β€” no return value, nothing to unwrap, just vibes. 🫢

🌈 SEE ALSO 🌈

Kernel file ./drivers/gpu/drm/amd/display/dc/dml/dcn32/dcn32_fpu.c


okay bye bestie 🫢 quick footer vibe check: source/version ./drivers/gpu/drm/amd/display/..., date October 2026, page dcn32_assign...ve_candidate(9). that's the whole page, mwah πŸ’‹

πŸ“¦ where this page comes from