drm_dp_tunne...allocated_bw(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– drm_dp_tunnel_get_allocated_bw β€” get the BW allocated for a DP tunnel πŸ’–

okay so bestie, welcome to the Kernel API Manual ✨ this one's about drm_dp_tunnel_get_allocated_bw, and it's genuinely such a little cutie β€” one job, does it well πŸŽ€


🌸 NAME 🌸

drm_dp_tunnel_get_allocated_bw β€” get the BW allocated for a DP tunnel πŸ’…


✨ SYNOPSIS ✨

int drm_dp_tunnel_get_allocated_bw (struct drm_dp_tunnel *tunnel );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • tunnel β€” the tunnel object πŸŒ€ that's the whole entire vibe, it's the only thing you pass in

πŸ’œ DESCRIPTION πŸ’œ

So this is the part where you ask the tunnel "hey bestie, how much BW do you have allocated rn?" and it tells you πŸ’–

It gets the current BW allocated for tunnel. Simple. Iconic. Main character energy.

But listen β€” there's a little lore here πŸ‘‘ After the tunnel is created / resumed and the BW allocation mode is enabled for it, the allocation doesn't just show up immediately. Nope. It becomes determined only after the first allocation request by the driver calling drm_dp_tunnel_alloc_bw 😌 so like, timing matters, iykyk.

🫢 it returns the BW allocated for the tunnel, or -1 if the allocation is undetermined. That -1 is your "not yet bestie, check back later" signal 🌸

🌈 SEE ALSO 🌈

  • Kernel file ./drivers/gpu/drm/display/drm_dp_tunnel.c β€” the whole squad lives here 🧚

And the rest of the tunnel besties, all of them, no cap:


and that's the whole page, bestie πŸ’…βœ¨ this little gem comes from ./drivers/gpu/drm/display and it's dated October 2026 β€” go forth and check your BW, ily, bye πŸŽ€πŸ¦‹πŸ’–

πŸ“¦ where this page comes from