calculate_alt_copy_time_us(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… calculate_alt_copy_time_us(9) β€” the Kernel API Manual glow-up ✨

okay bestie, so this one lives in the calculate_alt_copy_time_us(9) corner of the kernel API manual, and honestly? it's a lil math gremlin and i respect it 🫢


✨ NAME ✨

calculate_alt_copy_time_us β€” crunches out a tight upper bound for the copy time across, like, all the planes and streams πŸ”₯


πŸŽ€ SYNOPSIS πŸŽ€

unsigned int calculate_alt_copy_time_us (const struct
dml2_core_calcs_calculate_alternate_params *p );

🌸 ARGUMENTS 🌸

  • p β€” bestie… the manpage literally says -- undescribed -- 😭 so that's all we got. it's the const struct dml2_core_calcs_calculate_alternate_params * from the synopsis. no cap, that's the whole description.

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so this function's whole job is calculating a tight upper bound for the copy time over all planes and streams. and when we say "tight"? we mean it πŸ’… β€” it does the math assuming SVP0 and SVP1 cannot both overlap with prefetch (and prefetch is the one that potentially has the "most" amount of bytes to copy per dst line, so yeah, that's the spicy assumption).

the other iconic thing: it uses the exact NoOfDPP as calculated by DML β€” like, it does not take an input num_dpp param, she computes it herself πŸ‘‘. why? because we want the copy time calculation to be precise, so we can minimize FW latency / overhead. main character energy fr fr.


🌈 SEE ALSO 🌈


okay and before i go β€” the source path on this one is ./drivers/gpu/drm/amd/display/..., dated October 2026, and yes it's still calculate_alt_copy_time_us(9) at the bottom, we love a consistent footer πŸ“βœ¨ ty for coming to my ted talk, go read the kernel file, ily πŸ’œπŸ§š

πŸ“¦ where this page comes from