devm_mux_state_get_optional(9)

📦 version 7.3.1, in nixpkgs unstable

💅 devm_mux_state_get_optional(9) — from the Kernel API Manual, bestie

okay so picture this: you're deep in the kernel, you need a mux-state for a device, but optional — like, only if it's actually there. That's literally this function. It's the resource-managed girlie of the mux-state-getting family, and she's iconic for it. 🎀

✨ SYNOPSIS ✨

struct mux_state * devm_mux_state_get_optional (struct device *dev ,
   const char *mux_name );

like, that's the whole vibe. two args, one pointer back. slay. 💅

🌸 ARGUMENTS 🌸

  • dev — the device that needs a mux-state. she's the one asking, bestie. 👑
  • mux_name — the name identifying the mux-state. think of it as the @ handle you're looking up. 🔍

💖 RETURN 💖

so here's the vibe check on what you get back:

  • Pointer to the mux-state on success 🎉
  • an ERR_PTR with a negative errno on error 😭
  • or NULL if mux doesn't exist 🫥
fr fr, clock that NULL case — it's optional, remember? absence isn't an error here, it's just, like, not present. iykyk.

🦋 DESCRIPTION 🦋

The mux-state will automatically be freed on release. that's the whole point, bb — no manual cleanup era. devm handles it, you just live your life. ✨🧚

🌈 SEE ALSO 🌈

Kernel file ./drivers/mux/core.c — plus the whole friend group, all of them, no cap:

and that's the post 💌 this whole thing lives in ./drivers/mux, dated October 2026, and it's called devm_mux_state_get_optional(9) in case you forgot already 🙈 go forth and get those optional mux-states, bestie 🫶💜

📦 where this page comes from