usb_phy_roo...y_disconnect(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… usb_phy_roo...y_disconnect(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual ✨ β€” yes the title is literally cut off at usb_phy_roo...y_disconnect(9) and no we're not fixing it, that's just how it's printed, iykyk πŸŽ€


🌸 NAME 🌸

usb_phy_roothub_notify_disconnect β€” the disconnect notification girlie πŸ’« she's here to tell you a port peaced out.


πŸ¦‹ SYNOPSIS πŸ¦‹

int usb_phy_roothub_notify_disconnect (struct usb_phy_roothub
*phy_roothub , int port );

like, she takes two things and gives you back an int, periodt πŸ’…


πŸŽ€ ARGUMENTS πŸŽ€

  • phy_roothub β€” the phy of roothub, bestie. only relevant if the host is using a generic phy, so keep that vibe check in mind 🫢
  • port β€” the port index for the disconnect. literally just which port said bye πŸ‘‹

⭐ DESCRIPTION ⭐

so here's the tea: if the phy needs to get connection status, the callback can be used. that's it, that's the whole bit, no cap πŸ”₯


πŸ’– RETURN πŸ’–

0 if successful β€” slay πŸ‘‘ β€” and a negative error code otherwise 😭 (yes, negative, we don't do positive errors here)


🌈 SEE ALSO 🌈


ngl, if you're poking at generic phy connection status from a roothub, this is your girl. go read the kernel file if you want the deep lore πŸ“–βœ¨

and that's a wrap, bestie πŸ§šπŸ’œ this icon dropped from ./drivers/usb/core back in October 2026 β€” go off, kernel girlies πŸ“

πŸ“¦ where this page comes from