drm_dp_bw_c...g_efficiency(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… drm_dp_bw_channel_coding_efficiency(9) β€” NAME ✨

okay so bestie, this is a page from the Kernel API Manual and it's about drm_dp_bw_channel_coding_efficiency β€” aka the function that tells you how much of your DisplayPort link's bandwidth actually survives the encoding overhead. it's giving "how much of the pizza is crust" energy. πŸ•


🌈 SYNOPSIS 🌈

int drm_dp_bw_channel_coding_efficiency (bool is_uhbr );

πŸŽ€ ARGUMENTS πŸŽ€

  • is_uhbr β€” the vibe check flag: is this link using 128b/132b channel coding or not? that's literally all it wants to know. πŸ¦‹

πŸ’– DESCRIPTION πŸ’–

so this function returns the channel coding efficiency of whatever DP link type you hand it. and there are exactly two options in this whole situation, no in-between:

  • 8b/10b
  • 128b/132b β€” aka UHBR, main character energy πŸ‘‘

the corresponding overhead it's counting includes:

  • the 8b -> 10b pixel data to link symbol conversion overhead
  • the 128b -> 132b pixel data to link symbol conversion overhead
  • and for 128b/132b specifically, any link or PHY level control symbol insertion overhead β€” that's LLCP, FEC, PHY sync β€” see DP Standard v2.1 3.5.2.18 if you wanna read the receipts πŸ“–
ngl for 8b/10b the corresponding FEC overhead is BW allocation specific, and it's already included in the value returned by drm_dp_bw_overhead β€” so don't go double-counting it, bestie, i'm warning you 😭

and what does it actually give back? it returns the efficiency in the 100%/coding-overhead% ratio in 1ppm units. iconic. precise. slay. πŸ’…


🌸 SEE ALSO 🌸

kay so this is the part where the manpage just. lists everyone. the whole friend group. i'm not kidding, there are so many. but every single one is here because that's the rules 🫢

the main event:

  • Kernel file ./drivers/gpu/drm/display/drm_dp_helper.c

and then literally everyone else:

like. that's the whole roster. iykyk πŸ’€


okay that's the page!! it lives in ./drivers/gpu/drm/display, it's dated October 2026, and this whole little kernel-docs moment was brought to you by the Kernel API Manual. go forth and compute your coding efficiency, bestie β€” you're gonna ate it. πŸ’œβœ¨πŸŽ€

πŸ“¦ where this page comes from