subvp_subvp_admissable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… subvp_subvp_admissable πŸ’…

okay bestie, welcome to the Kernel API Manual ✨ this little cutie lives in the kernel API docs and she's here to answer one very specific question, so let's get into it 🫢


✨ NAME ✨

subvp_subvp_admissable β€” determine if subvp + subvp config is admissible πŸŽ€

Like, is this SubVP-on-SubVP situation actually allowed? That's the whole vibe check. πŸ’«


🌸 SYNOPSIS 🌸

bool subvp_subvp_admissable (struct dc *dc , struct dc_state *context );

She takes two things and gives you back a bool. Simple. Iconic. No cap. πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dc β€” the current DC state, aka where we're at right now πŸ’–
  • context β€” the new DC state that's about to be programmed, aka the glow-up we're considering ✨

⭐ DESCRIPTION ⭐

so here's the tea, bestie: SubVP + SubVP is admissible under the following conditions β€” and you have to match one of these, okay? πŸ‘‡

  • All SubVP pipes are < 120Hz OR
  • All SubVP pipes are >= 120hz

that's it. that's the whole rule. it's giving "simple but strict" and honestly? we respect it πŸ’… lowercase hz in the original and all, we're keeping it exactly as-is fr fr πŸ™ˆ

no mixing and matching, bestie β€” it's all-under-120 or all-at-least-120. pick a lane. 😭

πŸ”₯ RETURN πŸ”₯

True if admissible, false otherwise 🌈

(that lowercase false is canon, don't come for me πŸ’€)


πŸŽ€ SEE ALSO πŸŽ€

the whole friend group, gathered here for you 🫢:


and that's the page, bestie!! 🧚 source: ./drivers/gpu/drm/amd/display/..., dated October 2026 β€” go forth and check your refresh rates responsibly πŸ’œπŸ“

πŸ“¦ where this page comes from