typec_partne...num_altmodes(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

ok so this page is typec_partne...num_altmodes(9) from the Kernel API Manual (the name got truncated in the header, bestie, but it's typec_partner_set_num_altmodes) β€” and it does exactly what it says on the tin: it sets the number of available partner altmodes πŸ’…

🌸 SYNOPSIS 🌸

int typec_partner_set_num_altmodes (struct typec_partner *partner , int
num_altmodes );

πŸŽ€ ARGUMENTS πŸŽ€

  • partner β€” the partner we're updating, like the main character of this whole operation 🫢
  • num_altmodes β€” the number of altmodes we want to specify as available ✨

πŸ¦‹ DESCRIPTION πŸ¦‹

so here's the vibe: this routine is used to report the number of alternate modes supported by the partner. that's it, that's the job πŸ’–

⚠️ and listen β€” this value is *not* enforced in alternate mode registration routines. like, it's purely a report, no cap. nobody's gonna come check your math at registration time πŸ‘€

partner.num_altmodes is set to -1 on partner registration, which means "a valid value has not been set for it yet" β€” a lil placeholder era, if you will πŸ™ˆ

it returns 0 on success or a negative error number on failure. icon behavior, honestly 😌

πŸ”₯ SEE ALSO πŸ”₯

okay bestie, buckle up, because this list is long β€” all of these live in the Kernel file ./drivers/usb/typec/class.c and they're all part of the same typec friend group 🌈


and that's the whole page, periodt πŸ’œ this lil gem lives in ./drivers/usb/typec, dated October 2026, and yes the manual header and footer both say typec_partne...num_altmodes(9) because even manpages get truncated sometimes 😭 slay πŸŽ€

πŸ“¦ where this page comes from