ENUM MUX_FIRST_REG(9)
π enum mux_first_reg(9) β like, the whole vibe of the FIRST register, explained
okay bestie, so this page lives in the Kernel API Manual and it's all about enum mux_first_reg β yep, it literally defines the modes of access of the FIRST register. iconic behavior, honestly. that's the NAME section, we're done with it, slay π
β¨ SYNOPSIS β¨
here's the whole thing, exactly as it is, no cap:
enum mux_first_reg {
mux_f_mux ,
mux_f_gpio ,
mux_f_keep
};
look at her. three constants. zero drama. we love a concise queen π
πΈ Constants πΈ
okay so these are the three little options, and each one is doing something very specific β let me break it down:
mux_f_muxβ sets the corresponding pin to a fully-pinmux pin. like, committing to the mux life, fully.mux_f_gpioβ sets the corresponding pin to a GPIO or IOP pin. different path, still valid, we respect it π«Άmux_f_keepβ don't change it. keep it intact. leave her alone. she's fine. (this is the "no thoughts, just vibes" option ngl)
π SEE ALSO π
go look at the kernel file ./drivers/pinctrl/sunplus/sppctl.h β that's where all the lore lives. and while you're there, check out:
enum mux_master_reg(9)enum pinmux_type(9)struct grp2fp_map(9)
iykyk π
bestie reminder: every constant here keeps its exact meaning β mux_f_keep really does mean don't change (keep intact), so don't go touching pins that told you they're fine π
and that's the page!! mwah π this little gem comes from ./drivers/pinctrl/sunplus, dated October 2026 β and the man page itself is enum mux_first_reg(9), obviously, she's the main character β π¦
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms