tb_xdomain_alloc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

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

okay so this is tb_xdomain_alloc(9) from the Kernel API Manual, and it's literally the glow-up moment where a brand-new XDomain object gets born ✨


🌸 NAME 🌸

tb_xdomain_alloc β€” allocate a new XDomain object πŸ’–


✨ SYNOPSIS ✨

struct tb_xdomain * tb_xdomain_alloc (struct tb *tb , struct device
*parent , u64 route , const uuid_t *local_uuid , const uuid_t
*remote_uuid );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • tb β€” the domain where the XDomain belongs, yep, it lives here 🏠
  • parent β€” the parent device, and bestie, this is specifically the switch through which the other domain is reached πŸ”Œ (iykyk)
  • route β€” the route string used to reach the other domain πŸ›£οΈ
  • local_uuid β€” our local domain UUID, that's us πŸ’β€β™€οΈ
  • remote_uuid β€” the UUID of the other domain, and heads up, it's optional πŸ™ˆ

πŸ’œ DESCRIPTION πŸ’œ

So what it does: it allocates a new XDomain structure and hands you back a pointer to it. Slay. πŸ‘‘

But listen β€” and this is the important part β€” the object must be released by calling tb_xdomain_put. No leaving it lying around, that's not the vibe. 🫢


⭐ RETURN ⭐

  • a pointer to struct tb_xdomain when everything's cute and works 🌈
  • NULL in case of failure 😭

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/thunderbolt/xdomain.c 🧚 and all these icons:


and that's the whole page, no cap πŸ“

mwah πŸ’‹ β€” this one's brought to you from ./drivers/thunderbolt, dated October 2026, in all its tb_xdomain_alloc(9) glory. go off, king πŸ‘‘

πŸ“¦ where this page comes from