intel_dp_eff...ve_data_rate(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay so bestie, welcome to the Kernel API Manual πŸ’– this page is all about intel_dp_effective_data_rate β€” yes, the page header goes full truncation-core with intel_dp_eff...ve_data_rate(9), but the real NAME line says it returns the pixel data rate while accounting for BW allocation overhead. periodt πŸ’…


🫢 SYNOPSIS 🫢

int intel_dp_effective_data_rate (int pixel_clock , int bpp_x16 , int bw_overhead );

it’s giving <purple>an int return type</purple>, three int arguments, and zero mystery. slay.


🌸 ARGUMENTS 🌸

  • pixel_clock β€” the pixel clock in kHz, bestie ⏰
  • bpp_x16 β€” bits per pixel in .4 fixed point format πŸŽ€
  • bw_overhead β€” BW allocation overhead in 1ppm units. keep it in ppm, no cap 🧚

πŸ’… DESCRIPTION πŸ’…

Return the effective pixel data rate in kB/sec units, taking into account the provided SSC, FEC, and DSC BW allocation overhead. that’s the whole function, and it ate πŸ”₯

the overhead is the stuff you passed in as bw_overhead, and the function gives you back the effective pixel data rate in kB/sec. literally that’s the vibe πŸ¦‹


πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file: ./drivers/gpu/drm/i915/display/intel_dp.c β€” that’s the source file, no cap 🫢

also peek at these iconic little functions:


okay bye πŸ’– this gem comes from the ./drivers/gpu/drm/i915/display source/version corner, dated October 2026, and signed intel_dp_eff...ve_data_rate(9). mwah πŸ«ΆπŸŽ€

πŸ“¦ where this page comes from