usb4_usb3_port_match(9)

📦 version 7.3.1, in nixpkgs unstable

💅 usb4_usb3_port_match — the Kernel API Manual ✨

okay so bestie, welcome to usb4_usb3_port_match(9), the little function that answers the question every USB4 port has been dying to ask: is this USB 3.x port literally tunneled through me? 🌀🦋

🌸 NAME 🌸

usb4_usb3_port_match — matches a USB4 port device with a USB 3.x port device 💖 (yes bestie, it's a matchmaker, and honestly? it's serving cupid energy)

✨ SYNOPSIS ✨

bool usb4_usb3_port_match (struct device *usb4_port_dev , const struct
       fwnode_handle *usb3_port_fwnode );

that's the whole signature, no cap — copy it exactly, the compiler does NOT vibe with typos 😭

🎀 ARGUMENTS 🎀

  • usb4_port_dev — the USB4 port device 👑 this is our main character, the one doing the matching
  • usb3_port_fwnode — the USB 3.x port firmware node 🧚 the one being checked, the potential match, the love interest if you will

🔥 DESCRIPTION 🔥

okay so here's the tea 🍓: this function checks whether the USB 3.x port usb3_port_fwnode is tunneled through the USB4 port usb4_port_dev. That's it. That's the whole job. iykyk.

If the match is found it returns true 💖, and if it's not? false 💀. Simple. Iconic. No notes.

ngl, this function was designed to be used with the component framework — specifically with component_match_add. it's giving "built for a purpose" energy, and honestly we stan a function that knows its lane 🫶✨

🦋 SEE ALSO 🦋

go read those too, bestie, they're all part of the same thunderbolt family and they all ate 💅

and that's the whole page, periodt! 🎀 this cutie lives in ./drivers/thunderbolt, it's from October 2026, and it's brought to you by the Kernel API Manual — mwah, love that for us 💜✨🦋

📦 where this page comes from