dcn30_find_..._mclk_switch(9)
π NAME π
dcn30_find_dummy_latency_index_for_fw_based_mclk_switch β okay so bestie, this one finds the dummy_latency_index when MCLK switching is happening with firmware based vblank stretch enabled. The way it works is it literally just iterates through the table of dummy pstate latencies until it finds the lowest value that lets dm_allow_self_refresh_and_mclk_switch actually happen. That's it. That's the whole vibe. π¦
This is from the Kernel API Manual, btw, in case you were wondering where you wandered into. π
β¨ SYNOPSIS β¨
int dcn30_find_dummy_latency_index_for_fw_based_mclk_switch (struct dc
*dc , struct dc_state *context , display_e2e_pipe_params_st *pipes , int
pipe_cnt , int vlevel );
π ARGUMENTS π
dcβ the current DC state, like, right now, present tense, main character energy πcontextβ the new dc state, the glow-up version πpipesβ the DML pipe params, the whole cast of characters πpipe_cntβ how many DML pipes we're dealing with, the headcount fr fr π’vlevelβ the voltage level that DML went and calculated for us β‘
πΈ RETURN πΈ
It hands you back the lowest dummy_latency_index value. That's the whole gift. π
π¦ SEE ALSO π¦
Kernel file ./drivers/gpu/drm/amd/display/dc/dml/dcn30/dcn30_fpu.c β go read it, iykyk πβ¨
ngl bestie, the source path gets a little shy at the end there and just says ./drivers/gpu/drm/amd/display/... β respect the ellipsis, it's got mysterious energy π
That's a wrap, gorgeous! π This little cutie is dated October 2026, lives in the Kernel API Manual, and came straight out of ./drivers/gpu/drm/amd/display/.... Go forth and find those dummy latency indices β you ate. periodt. ππ
π¦ 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