tb_xdomain_disable_paths(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ tb_xdomain_disable_paths β€” the Kernel API Manual glow-up ✨

okay so bestie, you know how tb_xdomain_enable_paths gets all the hype? this is its iconic counterpart, the function from the Thunderbolt kernel API docs (tb_xdomain_disable_paths(9)) that cleans up the DMA path situation when the party's over. πŸŽ€


🌸 NAME 🌸

tb_xdomain_disable_paths β€” Disable DMA paths for XDomain connection πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

int tb_xdomain_disable_paths (struct tb_xdomain *xd , int transmit_path
, int transmit_ring , int receive_path , int receive_ring );

like, that's the whole signature, no cap ✨


🫢 ARGUMENTS 🫢

  • xd β€” the XDomain connection, obvi πŸ’–
  • transmit_path β€” the HopID we're using to send out packets
  • transmit_ring β€” the DMA ring we use to send out packets
  • receive_path β€” the HopID the other end is using to send packets to us (so it receives on our side, iykyk)
  • receive_ring β€” the DMA ring used to receive packets from receive_path πŸ¦‹

πŸ‘‘ DESCRIPTION πŸ‘‘

okay so basically: this does the literal opposite of tb_xdomain_enable_paths. 🀭

After you call this, the caller is not expected to use the rings anymore β€” like, they're closed, bestie, move on. πŸ’€

Passing -1 as a path/ring parameter means "don't care" β€” yes, -1 is the universal vibe of "idk, whatever works". Normally though, callers should pass the same values here that they do when the paths are enabled, because consistency ate and left no crumbs. πŸ”₯


⭐ RETURN ⭐

  • 0 on success πŸŽ‰
  • negative errno otherwise 😭

🌈 SEE ALSO 🌈

Kernel file ./drivers/thunderbolt/xdomain.c, plus the whole squad:

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_find_by_uuid(9), tb_xdomain_find_by_link_depth(9), tb_xdomain_find_by_route(9), tb_register_property_dir(9), tb_unregister_property_dir(9) πŸ’œ


ngl this whole page lives in ./drivers/thunderbolt, and it's serving October 2026 energy from the tb_xdomain_disable_paths(9) volume β€” anyway, that's the tea, bestie, go disable those paths responsibly πŸ§šπŸ’–
πŸ“¦ where this page comes from