usb4_dp_port...ed_bandwidth(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… usb4_dp_port_requested_bandwidth(9) β€” Kernel API Manual ✨

okay so bestie, you found the page for usb4_dp_port_requested_bandwidth(9) and honestly? it's a little cutie. it lives in the Kernel API Manual, it's a kernel function, and it does exactly one thing but it does it slayfully. let's get into it πŸŽ€


✨ NAME ✨

usb4_dp_port_requested_bandwidth β€” Read requested bandwidth πŸ’–

like, that's the whole job. reading the bandwidth that's been requested. no cap.


πŸ¦‹ SYNOPSIS πŸ¦‹

int usb4_dp_port_requested_bandwidth (struct tb_port *port );

that's it. that's the whole call. one arg, one int coming back at you. iconic behavior tbh.


🌸 ARGUMENTS 🌸

  • port β€” the DP IN adapter. that's the thing you're asking about. hand it over and it'll tell you what's up 🫢

πŸ‘‘ DESCRIPTION πŸ‘‘

so here's the vibe: this function reads the DPCD (graphics driver) requested bandwidth and returns it in Mb/s. that's megabits per second, for the record, so don't go confusing it with megabytes or the whole thing falls apart 😭

and the important little detail β€” it takes the programmed granularity into account. meaning it's not just spitting raw numbers back at you, it's doing the math with the granularity setting so the answer actually means something.

highkey a thoughtful function. we stan.


πŸ’€ RETURN πŸ’€

here's what you can get back, and literally every one of these matters, so pay attention bestie 🧚

  • Requested bandwidth in Mb/s β€” On success. this is the good outcome, the main character ending 🌈
  • -EOPNOTSUPP β€” If the adapter does not support bandwidth allocation mode. like, it can't do the thing. respectfully decline energy πŸ™ˆ
  • ENODATA β€” If there is no active bandwidth request from the graphics driver. nobody asked for anything, so there's nothing to report πŸ’€
  • Negative errno β€” On failure. the classic catch-all for when stuff just goes wrong. not a slay, but it happens 😭
lowkey important: watch out for that ENODATA vs the negative errno situation β€” they're listed separately, and ENODATA is written without the leading dash in this page. don't come for me, that's just how it's documented. πŸ™ˆ

πŸŽ€ SEE ALSO πŸŽ€

okay this list is long long, so buckle up. also worth knowing: the kernel file this all lives in is ./drivers/thunderbolt/usb4.c ⭐

the whole thunderbolt/usb4 extended family, in the order the page gives 'em:

yeah. seventy-something friends. it's giving family reunion πŸ“


πŸ’œ and that's the whole page bestie πŸ’œ

shoutout to ./drivers/thunderbolt for the source, and to October 2026 for the date β€” this page is stamped and sealed and ready for you. go read some bandwidth. you got this. mwah πŸ’…βœ¨πŸ¦‹

πŸ“¦ where this page comes from