_dpu_vbif_ap...mic_ot_limit(9)
π _dpu_vbif_ap...mic_ot_limit(9) β from the Kernel API Manual, bestie
okay so real talk, this one lives in the Kernel API Manual and the function name got chopped in the header like _dpu_vbif_ap...mic_ot_limit β tragic, I know, but the full name is in NAME and it ate π
β¨ NAME β¨
_dpu_vbif_apply_dynamic_ot_limit β literally figures out your OT based on the usecase parameters π
π¦ SYNOPSIS π¦
void _dpu_vbif_apply_dynamic_ot_limit (struct dpu_hw_vbif *vbif , u32
*ot_lim , struct dpu_vbif_set_ot_params *params );
πΈ ARGUMENTS πΈ
vbifβ pointer to the hardware vbif driver πot_limβ pointer to the OT limit that's gonna get modified, so yeah, she's mutable πparamsβ pointer to the usecase parameters π
β SEE ALSO β
the kernel file, no cap:
./drivers/gpu/drm/msm/disp/dpu1/dpu_vbif.c
and the whole friend group π«Ά:
_dpu_vbif_wait_for_xin_halt(9)_dpu_vbif_get_ot_limit(9)dpu_vbif_set_ot_limit(9)dpu_vbif_set_qos_remap(9)dpu_vbif_clear_errors(9)dpu_vbif_init_memtypes(9)
lowkey the entire page is just those 3 args and a friend list, but she's iconic for it π
ok that's the whole thing, mwah π β this came out of ./drivers/gpu/drm/msm/disp/dpu1 and it's dated October 2026, and yes we're still gonna be reading kernel docs in 2026, slay ππ§π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms