tb_switch_tmu_configure(9)

📦 version 7.3.1, in nixpkgs unstable

✨ tb_switch_tmu_configure(9) ✨

okay bestie, welcome to the Kernel API Manual 💅 — yes this is a real function, yes it lives in the Thunderbolt TMU world, and yes we're gonna get through it together 🫶

🌸 NAME 🌸

tb_switch_tmu_configure — configure the TMU mode ✨ literally what it says on the tin, no cap

🦋 SYNOPSIS 🦋

int tb_switch_tmu_configure (struct tb_switch *sw , enum
       tb_switch_tmu_mode mode );

bestie it's one function call, you got this 💖

🎀 ARGUMENTS 🎀

  • sw — the Router whose mode you're changing 👑 like, the actual device we're messing with
  • mode — the Mode to configure 🌈 i.e. which mode you want it set to

💜 DESCRIPTION 💜

So here's the tea ☕: this call selects the TMU mode that gets enabled when tb_switch_tmu_enable is next called. That's it. That's the whole vibe. You're not turning anything on right now — you're just picking which mode will be used the next time enable happens. it's giving "setting up the outfit the night before" energy 👗✨

🔥 RETURN 🔥

  • 0 — On success 🎉 slay, it worked
  • -EOPNOTSUPP — If the requested mode is not possible (not supported by the router and/or topology) 😭 like, the hardware just said no. this is your "not supported by the router and/or topology" situation, fr fr
  • Negative errno — Another error occurred 💀 some other error showed up, check the errno bestie

🧚 SEE ALSO 🧚

Kernel file ./drivers/thunderbolt/tmu.c — and the whole friend group 💖

⚠️ friendly heads up: the -EOPNOTSUPP case is real — if the router and/or topology doesn't support the mode you asked for, you're getting that error back, no cap. always vibe check your topology first 🫡

and that's the page, bestie 🎀 it came from ./drivers/thunderbolt, dated October 2026, and it's part of the Kernel API Manual — go forth and configure those TMU modes responsibly 💅✨

📦 where this page comes from