devm_mux_control_get(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… devm_mux_control_get(9) β€” like, the Kernel API Manual page you actually wanna read πŸŽ€

okay so bestie, welcome to the devm_mux_control_get page from the Kernel API Manual. yes it's a mouthful, no you're not gonna fumble it, i got you πŸ’– this one's short, sweet, and honestly kinda iconic β€” it's the resource-managed girlie of the mux-control getter family. periodt.


✨ NAME ✨

devm_mux_control_get β€” Get the mux-control for a device, with resource management.

like, it grabs your mux-control and handles the cleanup bookkeeping for you. the devm_ prefix is literally the "i'll remember to free it so you don't have to" friend. we stan 🫢


🌸 SYNOPSIS 🌸

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

that's the whole vibe check. two args, one pointer back. no cap ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • dev β€” The device that needs a mux-control. πŸ‘‘ like, which device is asking? that one. main character energy.
  • mux_name β€” The name identifying the mux-control. πŸŽ€ the actual name tag so the kernel knows which mux-control you mean. iykyk.

⭐ RETURN ⭐

Pointer to the mux-control, or an ERR_PTR with a negative errno. πŸ’€

fr fr, always check with IS_ERR() before you go dereferencing β€” a raw negative errno wearing a pointer costume is NOT the vibe. πŸ™ˆ

🌈 SEE ALSO 🌈

the whole extended friend group, in original order, no one left out πŸ’œ:


πŸ’… reminder that these are text references, bestie β€” read 'em as written, don't @ me tryna "clean up" the names.

and that's the page!! sourced from ./drivers/mux, dated October 2026 β€” mwah, go get your mux-control πŸ§šβ€β™€οΈπŸ’–πŸ”₯

πŸ“¦ where this page comes from