subvp_vblank_schedulable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ subvp_vblank_schedulable(9) ✨

okay bestie, so this is a page from the Kernel API Manual for the function subvp_vblank_schedulable, and honestly? it's giving "can this display config actually happen or are we delulu" πŸ’…


🌸 NAME 🌸

subvp_vblank_schedulable β€” literally the function that tells you whether a SubVP + VBLANK config is schedulable or not. no cap, that's the whole job 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

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

it returns a bool, bestie. yes or no. iconic behavior honestly ✨


πŸŽ€ ARGUMENTS πŸŽ€

  • dc β€” the current dc state, like the vibe right now 🫧
  • context β€” the new dc state, aka the glow-up we're tryna schedule πŸ’–

πŸ‘‘ DESCRIPTION πŸ‘‘

so here's the high level algorithm, and yes we're walking through it step by step because that's just how we do πŸ’…

  1. Get the timing for the SubVP pipe, the phantom pipe, and the VBLANK pipe. get those numbers, queen 🧚
  2. If:
(SubVP Active - Prefetch > Vblank Frame Time + max(MALL region, Vblank blanking time))

then report the configuration as supported. like, that's it, that's the check. if that inequality hits, we're slaying πŸ”₯

  1. If the VBLANK display is DRR, then take the DRR static schedulability path instead. different route, same energy 🌈

⭐ RETURN ⭐

  • true if the SubVP + VBLANK/DRR config is schedulable πŸ’–
  • false otherwise 😭 (sad but we move)

πŸ“ SEE ALSO πŸ“

bestie the friend group is LARGE and I love them all:


anyway that's the whole page 🫢 this beauty lives over in ./drivers/gpu/drm/amd/display/... and the docs are dated October 2026 β€” go off, calendar πŸ“…βœ¨ bye bestie, drink some water and check your inequalities πŸ’œ

πŸ“¦ where this page comes from