tb_xdomain_find_by_route(9)

💅 tb_xdomain_find_by_route(9) 💅

okay so bestie, welcome to the Kernel API Manual ✨ this one is literally tb_xdomain_find_by_route, and it does exactly what it says on the tin: finds an XDomain by route string. no cap.

🌸 NAME 🌸

tb_xdomain_find_by_route — Find an XDomain by route string 💖

✨ SYNOPSIS ✨

struct tb_xdomain * tb_xdomain_find_by_route (struct tb *tb , u64 route
);

🎀 ARGUMENTS 🎀

• tb — the domain where the XDomain belongs to, periodt.
• route — the XDomain route string. iconic.

💖 DESCRIPTION 💖

So the way this works is: it finds the XDomain by walking through the Thunderbolt topology below tb 🦋.

The returned XDomain will have its reference count increased, so the caller needs to call tb_xdomain_put when it is done with the object. don’t forget, bestie 😭.

This will find all XDomains, including the ones that are not yet added to the bus (handshake is still in progress). yep, even the mid-handshake girlies 💅.

🚨 the caller needs to hold tb->lock. this is not a drill, hold the lock.

🔥 RETURN 🔥

Pointer to struct tb_xdomain, or NULL if not found.

🦋 SEE ALSO 🦋

Kernel file ./drivers/thunderbolt/xdomain.c — plus the whole friend group:

• tb_xdomain_response(9)
• tb_xdomain_request(9)
• tb_register_protocol_handler(9)
• tb_unregister_protocol_handler(9)
• tb_register_service_driver(9)
• tb_unregister_service_driver(9)
• tb_service_properties_changed(9)
• tb_xdomain_alloc(9)
• tb_xdomain_add(9)
• tb_xdomain_remove(9)
• tb_xdomain_unregister(9)
• tb_xdomain_lane_bonding_enable(9)
• tb_xdomain_lane_bonding_disable(9)
• tb_xdomain_alloc_in_hopid(9)
• tb_xdomain_alloc_out_hopid(9)
• tb_xdomain_release_in_hopid(9)
• tb_xdomain_release_out_hopid(9)
• tb_xdomain_enable_paths(9)
• tb_xdomain_disable_paths(9)
• tb_xdomain_find_by_uuid(9)
• tb_xdomain_find_by_link_depth(9)
• tb_register_property_dir(9)
• tb_unregister_property_dir(9)

---

and that’s the tea ☕ source: ./drivers/thunderbolt, version/date: October 2026, and the manual page is tb_xdomain_find_by_route(9) 💖 slay, bye 🫶