dpu_vbif_set_ot_limit(9)
π dpu_vbif_set_ot_limit π
okay so welcome to the Kernel API Manual, bestie β this is the page for dpu_vbif_set_ot_limit, and yes we are going to get into it β¨
πΈ NAME πΈ
dpu_vbif_set_ot_limit β it sets the OT based on the usecase & configuration parameters. that's the whole vibe. no cap π«Ά
β¨ SYNOPSIS β¨
void dpu_vbif_set_ot_limit (struct dpu_kms *dpu_kms , struct
dpu_vbif_set_ot_params *params );
it's a void function, so likeβ¦ it returns nothing. it just does. main character energy honestly π
π ARGUMENTS π
dpu_kmsβ the DPU handler. that's your context, your whole situation, iykyk.paramsβ a pointer to the usecase parameters. literally pointing at the parameters of the usecase. slay.
π¦ DESCRIPTION π¦
okay so real talk β note that this function would block, waiting for the bus halt. like it will sit there and wait. π«Ά not me warning you but also yes, me warning you. plan accordingly bestie ππ
π SEE ALSO π
- the kernel file
./drivers/gpu/drm/msm/disp/dpu1/dpu_vbif.cβ that's where the magic lives, go look π _dpu_vbif_wait_for_xin_halt(9)_dpu_vbif_apply_dynamic_ot_limit(9)_dpu_vbif_get_ot_limit(9)dpu_vbif_set_qos_remap(9)dpu_vbif_clear_errors(9)dpu_vbif_init_memtypes(9)
all of them. every single one. the whole friend group π§π
and that's the page!! it lives in ./drivers/gpu/drm/msm/disp/dpu1, dated October 2026 β mwah, go read the source, ily, bye πβπ
π¦ 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