mux_state_try_select_delay(9)

📦 version 7.3.1, in nixpkgs unstable

✨ mux_state_try_select_delay 💅

okay so this is a page from the Kernel API Manual, bestie — it's called mux_state_try_select_delay(9) and it's basically the "try before you commit" of multiplexer states 🎀

🌸 NAME 🌸

mux_state_try_select_delay — Try to select the given multiplexer state. literally what it says on the tin, no cap ✨

🦋 SYNOPSIS 🦋

int mux_state_try_select_delay (struct mux_state *mstate , unsigned int
delay_us );

💖 ARGUMENTS 💖

  • mstate — The mux-state to select. this is the one you're trying to snag 👑
  • delay_us — The time to delay (in microseconds) if the mux state is changed. yes bestie, microseconds, she's precise 🕰️

🌈 DESCRIPTION 🌈

So here's the tea ☕: on successfully selecting the mux-state, its mux-control will be locked until mux_state_deselect is called. it's giving "claimed, do not disturb" energy 🔒

Which means — and this is the important part, fr fr — make sure to call mux_state_deselect when the operation is complete and the mux-control is free for others to use. don't be that girl who holds the lock forever 🙈

but do NOT call mux_state_deselect if mux_state_try_select fails. that's the vibes check failing, and you don't get to clean up something you never got 💀

⭐ RETURN ⭐

  • 0 when the mux-state has been selected — slay, you got it 💅
  • a negative errno on error
  • Specifically -EBUSY if the mux-control is contended. someone else is already in there, try again later bestie 😭

🫶 SEE ALSO 🫶

Kernel file ./drivers/mux/core.c plus the whole friend group:

and that's the whole page, bestie 🧚 this little gem lives in ./drivers/mux, dated October 2026, and it's part of the Kernel API Manual — go forth and select responsibly, mwah 💜🌸

mux_state_try_select_delay(9) — periodt. 👑

📦 where this page comes from