typec_retimer_unregister(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… typec_retimer_unregister(9) β€” from the Kernel API Manual, bestie πŸŽ€

okay so real talk, this one's a little send-off page. it's typec_retimer_unregister, and it lives in the Kernel API Manual (yes, that's the manual name, we're being official today ✨). think of it as the "bye babe" to typec_retimer_register's "heyyy πŸ‘‹". no cap, it's short, but it's important, so let's get into it πŸ¦‹


🌸 NAME 🌸

typec_retimer_unregister β€” literally just unregistering a retimer device. that's it, that's the vibe πŸ’…


✨ SYNOPSIS ✨

void typec_retimer_unregister (struct typec_retimer *retimer );

it returns void, meaning it gives you nothing back β€” not even a little status code, so don't go looking for one πŸ™ˆ


πŸŽ€ ARGUMENTS πŸŽ€

  • retimer β€” a USB Type-C Connector retimer. that's your girl, the one you're about to unregister 🫢

πŸ”₯ DESCRIPTION πŸ”₯

unregisters a retimer that was registered with typec_retimer_register. that's the whole plot 😭 like, it's giving "closing the loop", it's giving "cleanup era". you registered it, now you're sending it off. iconic behaviour tbh πŸ‘‘

ngl, this is the counterpart call, so if you never called typec_retimer_register in the first place, you're doing unregister wrong bestie πŸ’€

🌈 SEE ALSO 🌈

go read typec_retimer_register(9) if you want the origin story, fr fr ⭐


and that's the page!! 🧚 source is ./drivers/usb/typec, dated October 2026 β€” mwah, ty for coming to my ted talk, see you in the next manpage πŸ’œπŸŒΈπŸ“

πŸ“¦ where this page comes from