usb4_port_r..._sector_size(9)

📦 version 7.3.1, in nixpkgs unstable

💅 usb4_port_retimer_nvm_sector_size(9) 🎀

ok so this is a page from the Kernel API Manual, section 9 — yes bestie, we're in the deep kernel lore now, and this one is genuinely cute. it's all about asking a retimer "hey, how big are your NVM sectors?" and honestly? iconic behavior.

✨ NAME ✨

usb4_port_retimer_nvm_sector_size — read retimer NVM sector size 🦋

like, literally that. it reads the sector size. no cap.

🌸 SYNOPSIS 🌸

int usb4_port_retimer_nvm_sector_size (struct tb_port *port , u8 index );

that's the whole thing. two args, one int coming back at you. we love a simple signature 💖

🫶 ARGUMENTS 🫶

  • port — the USB4 port, aka the little doorway you're asking about. main character of this story.
  • index — the retimer index, like the seat number of whichever retimer you're pointing at 🎀

👑 DESCRIPTION 👑

so what it does: it reads the NVM sector size (in bytes 🍓) of a retimer at index.

and why do we care?? because this very operation can be used to figure out whether the retimer supports NVM upgrade — for example. that's the vibe check: if it answers with a sensible sector size, the upgrade story is plausibly real. iykyk ✨

🔥 RETURN 🔥

  • Sector size in bytes 💅
  • -ENODEV — if there's no retimer at index 😭 (bestie, you pointed at an empty seat)
  • Negative errno — in case of an error 💀
ngl, watch out for that second one — -ENODEV is the "nobody's home" signal, and negative errnos generally mean something went sideways. don't ignore them, fr fr.

🌈 SEE ALSO 🌈

okay this list is long. like, unreasonably long. but every single one of these is invited to the group chat, so here we go — kernel file ./drivers/thunderbolt/usb4.c, plus:

periodt. that's the whole crew 🧚

and that's the page!! tysm for reading, she's niche but she's everything. this one lives in ./drivers/thunderbolt and the page is dated October 2026 — mwah, bye bestie 💜💅✨

📦 where this page comes from