mux_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, this is mux_get(9) from the Kernel API Manual πŸ’– like, the whole point is getting the mux-control for a device, and yes we’re gonna cover every tiny detail. no cap.

🌸 NAME 🌸

mux_get β€” get the mux-control for a device. πŸ‘‘

✨ SYNOPSIS ✨

the whole vibe is:

       struct mux_control * mux_get (struct device *dev , const char *mux_name
       , unsigned int *state , bool optional , struct device_node *node );

πŸ’… ARGUMENTS πŸ’…

  • dev β€” the device that needs a mux-control. 🫢
  • mux_name β€” the name identifying the mux-control. πŸŽ€
  • state β€” pointer to where the requested state is returned, or NULL when the required multiplexer states are handled by other means. literally important info, bestie.
  • optional β€” whether to return NULL and silence errors when mux doesn't exist. lowkey the chill setting, iykyk.
  • node β€” the device nodes, use dev->of_node if it is NULL. πŸ¦‹

πŸ¦‹ RETURN πŸ¦‹

on success you get a pointer to the mux-control, periodt. on error? an ERR_PTR with a negative errno. and if optional is true and mux doesn't exist, you get NULL β€” no cap. 😭

🌈 SEE ALSO 🌈

bestie, the whole SEE ALSO squad is:

πŸ’– source/version: ./drivers/mux Β· date: October 2026 Β· catch you later, bestie! 🫢

πŸ“¦ where this page comes from