mux_control_get(9)

💖 NAME 💖

okay so bestie, this is the manual for mux_control_get(9) — straight from the Kernel API Manual — and it's literally about grabbing the mux-control for a device. no cap, that's the whole vibe: get the mux-control for a device ✨

✨ SYNOPSIS ✨

struct mux_control * mux_control_get (struct device *dev , const char *mux_name );

🎀 ARGUMENTS 🎀

• dev — the device that needs a mux-control. it's giving “please hand me the mux, I have main character energy” 👑
• mux_name — the name identifying the mux-control. this is the ID that tells you which one, iykyk 🔍

🌸 RETURN 🌸

you get back a pointer to the mux-control 🫶 — or an ERR_PTR with a negative errno 😭. that's the whole return situation, fr fr.

🦋 SEE ALSO 🦋

go peek at the Kernel file ./drivers/mux/core.c, plus the whole squad: struct mux_state(9), struct devm_mux_state_state(9), mux_chip_alloc(9), mux_chip_register(9), mux_chip_unregister(9), mux_chip_free(9), devm_mux_chip_alloc(9), devm_mux_chip_register(9), mux_control_states(9), mux_control_select_delay(9), mux_state_select_delay(9), mux_control_try_select_delay(9), mux_state_try_select_delay(9), mux_control_deselect(9), mux_state_deselect(9), mux_get(9), mux_control_get_optional(9), mux_control_put(9), devm_mux_control_get(9), mux_state_get(9), __devm_mux_state_get(9), devm_mux_state_get_from_np(9), devm_mux_state_get_optional(9), devm_mux_state_get_selected(9), devm_mux_state_get_optional_selected(9).

okay bye bestie 💅 — cute sign-off: the source/version footer says ./drivers/mux, and the date is October 2026 ✨