intel_link_b...ute_pipe_bpp(9)
π intel_link_bw_compute_pipe_bpp(9)
okay so bestie, welcome to the Kernel API Manual, and today's main character is intel_link_bw_compute_pipe_bpp β yes that's a mouthful, yes it ate, let's get into it π
β¨ NAME β¨
intel_link_bw_compute_pipe_bpp β literally computes the pipe bpp, but like... limited by the max link bpp π no cap.
πΈ SYNOPSIS πΈ
bool intel_link_bw_compute_pipe_bpp (struct intel_crtc_state *crtc_state
);
it's giving "one argument, one bool, done" energy π
π¦ ARGUMENTS π¦
crtc_stateβ the crtc state π«Ά that's it, that's the whole argument. she's simple, she's iconic.
π DESCRIPTION π
so the way that this works is: this function computes the pipe bpp limited by the CRTC's maximum link bpp. iykyk β¨
Encoders can call this function during state computation β but only in the simple case, where the link bpp will always match the pipe bpp. that's the vibe. π§
and who is that simple case for, you ask? literally all non-DP encoders. meanwhile DP encoders are out here using a link bpp lower than pipe bpp in case of DSC compression β different journey, different lore ππ
Returns true in case of success π and returns false if the pipe bpp would need to be reduced below its valid range. like β if she'd have to go below her valid range, that's a no from her π
β SEE ALSO β
- Kernel file:
./drivers/gpu/drm/i915/display/intel_link_bw.cβ go read it bestie, it's right there π₯ intel_link_bw_init_limits(9)__intel_link_bw_reduce_bpp(9)intel_link_bw_set_bpp_limit_for_pipe(9)intel_link_bw_atomic_check(9)
ngl this whole friend group lives in ./drivers/gpu/drm/i915/display and honestly? they're all slaying in their own way π
and that's the tea, fr fr π this page came to you courtesy of ./drivers/gpu/drm/i915/display, dated October 2026, and titled intel_link_b...ute_pipe_bpp(9) β 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