dcn32_subvp...k_admissable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dcn32_subvp_vblank_admissable β€” like, the whole vibe check

okay so bestie, welcome to the Kernel API Manual ✨ you're looking at dcn32_subvp_vblank_admissable(9), and yes the page header is doing that truncated thing (dcn32_subvp...k_admissable(9)) because apparently even manpages have a character limit, iconic behavior honestly πŸŽ€


🌸 NAME 🌸

dcn32_subvp_vblank_admissable β€” determine if SubVP + Vblank config is admissible πŸ¦‹

Like, is this configuration allowed? That's the whole question. She's a yes/no girlie.


✨ SYNOPSIS ✨

bool dcn32_subvp_vblank_admissable (struct dc *dc , struct dc_state
*context , int vlevel );

Returns a bool, takes a struct dc *, a struct dc_state *, and an int. That's it. That's the whole signature πŸ’–


🫢 ARGUMENTS 🫢

  • dc β€” the current DC state. Like, what's happening right now, the present-tense of the display, no cap.
  • context β€” the new DC state that's about to be programmed. The future. The main character we're about to install πŸ‘‘
  • vlevel β€” the voltage level, and it's calculated by DML. Not you, not me. DML did the math. We respect DML's math πŸ”₯

πŸŽ€ DESCRIPTION πŸŽ€

So here's the tea, bestie: SubVP + Vblank is admissible under the following conditions. And listen, all of these have to hit β€” it's giving strict vibes πŸ’…

  • Config must have 2 displays (i.e., 2 non-phantom master pipes). Literally two. Not one, not three. Two. The phantom ones don't count, they're not real, they're phantom, the name is right there πŸ™ˆ
  • One display is SubVP. Just one. The other one is doing its own thing.
  • The other display must not have Freesync capability. Sorry to the Freesync girlies, this specific config says no 😭
  • DML must have output DRAM clock change support as SubVP + Vblank. If DML didn't output it, it's not happening, periodt.
  • The potential vblank display must not be PSR capable. PSR-capable? Then this configuration isn't the one, bestie πŸ’€
ngl these conditions are cumulative β€” it's an "and" situation, not an "or" situation. Every single box gets checked or the whole thing falls apart 🧚

🌈 RETURN 🌈

  • True if admissible πŸ’– slay, it works.
  • false otherwise πŸ’€ she's not the one.

⭐ SEE ALSO ⭐

Go read the source, bestie, it's all right there in the kernel file πŸ‘‘

./drivers/gpu/drm/amd/display/dc/resource/dcn32/dcn32_resource_helpers.c

And the whole friend group of related functions β€” these are her sisters fr fr:


mwah πŸ’œ this page came to you straight from ./drivers/gpu/drm/amd/display/... (the Kernel API Manual, October 2026 issue) β€” and the title up top is still dcn32_subvp...k_admissable(9) because we don't abbreviate and we don't apologize βœ¨πŸ¦‹πŸŒΈ bye bestie, go check your master pipes πŸŽ€

πŸ“¦ where this page comes from