intel_dp_tun...te_stream_bw(9)

📦 version 7.3.1, in nixpkgs unstable

💖 NAME 💖

intel_dp_tunnel_atomic_compute_stream_bw — okay so this is the one that computes the BW (bandwidth, bestie, not "boyfriend") that a DP tunnel stream needs ✨

🎀 SYNOPSIS 🎀

int intel_dp_tunnel_atomic_compute_stream_bw (struct intel_atomic_state *state,
                                              struct intel_dp *intel_dp,
                                              const struct intel_connector *connector,
                                              struct intel_crtc_state *crtc_state);

🌸 ARGUMENTS 🌸

  • state — the atomic state, aka the whole vibe check in progress
  • intel_dp — the DP object itself, main character energy fr
  • connector — the connector that's using intel_dp, iykyk
  • crtc_state — the state of the CRTC belonging to the given DP tunnel stream

🦋 DESCRIPTION 🦋

So what this does: it computes the BW that the CRTC requires (the CRTC is the DP tunnel stream here, love that for us), and then it stores that BW into the DP tunnel state that contains the stream, inside state. Slay 💅

⚠️ Real talk though — before you re-calculate a BW requirement in the crtc_state state, the old BW requirement computed by this function must be cleared first by calling intel_dp_tunnel_atomic_clear_stream_bw. Not me warning you twice. It's literal. Clear it first. Periodt.

It returns 0 in case of success, and a negative error code otherwise. That's the whole contract, no cap 💀

👑 SEE ALSO 👑

Kernel file ./drivers/gpu/drm/i915/display/intel_dp_tunnel.c — go read it, it's giving lore ✨

🌈 that's the whole page, bestie! shipped from ./drivers/gpu/drm/i915/display, dated October 2026, and yeah the title got squished down to intel_dp_tun...te_stream_bw(9) in the corner bc terminal columns are haters 🙈 stay hydrated and clear your stream BW before recomputing 💜🫶

📦 where this page comes from