mux_control_...select_delay(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… mux_control_try_select_delay(9) ✨

okay so bestie, welcome to the Kernel API Manual β€” yes we're in the kernel docs now, main character energy only πŸŽ€ this one's about mux_control_try_select_delay, and it's lowkey a baddie.


🌸 NAME 🌸

mux_control_try_select_delay β€” try to select the given multiplexer state. note the "try", bestie, it's giving "we'll see" energy πŸ’…


⭐ SYNOPSIS ⭐

int mux_control_try_select_delay (struct mux_control *mux , unsigned int
state , unsigned int delay_us );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • mux β€” the mux-control that's gonna get asked so politely to change its state 🫢
  • state β€” the new requested state, the whole point of the operation, the moment ✨
  • delay_us β€” how long to delay, in microseconds, if the mux state actually changes. like a little pause for dramatic effect πŸ’œ

πŸ”₯ DESCRIPTION πŸ”₯

so when you successfully select the mux-control state, it gets locked until mux_control_deselect is called. no cap. it's yours now πŸ‘‘

🚨 so fr fr, make sure you call mux_control_deselect when the operation is complete and the mux-control is free for others to use. but β€” and this is the important part β€” do not call mux_control_deselect if mux_control_try_select fails. that's not slay, that's a bug 😭

🌈 RETURN 🌈

  • 0 β€” when the mux-control state has the requested state, we love a success story πŸ’–
  • a negative errno on error. specifically -EBUSY if the mux-control is contended β€” i.e. someone else is already on it, it's giving "occupied" πŸ™ˆ

🧚 SEE ALSO 🧚

the whole friend group 🫢:


anyway that's the whole page, you ate that πŸ’…βœ¨ this came straight out of ./drivers/mux, dated October 2026 β€” mwah, go read the kernel source bestie, ily πŸŽ€πŸ’–

πŸ“¦ where this page comes from