intel_link_b...ute_pipe_bpp(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

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 ⭐


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