pcs_get_pin_by_offset(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pcs_get_pin_by_offset β€” a Kernel API Manual moment (section 9, bestie)

okay so this is pcs_get_pin_by_offset(9) from the Kernel API Manual, and yes we're getting into pinctrl internals, but don't panic β€” it's literally a one-liner of a concept and it's giving "small but mighty" ✨


🌸 NAME 🌸

pcs_get_pin_by_offset β€” get a pin index based on the register offset

like, you give it an offset, it gives you back a pin index. that's the whole vibe. πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

int pcs_get_pin_by_offset (struct pcs_device *pcs , unsigned offset );

one function, two args, returns an int. no cap, that's it. πŸ’–


🧚 ARGUMENTS 🧚

  • pcs β€” the pcs driver instance 🌈 (your main character struct, the whole reason we're here)
  • offset β€” register offset from the base ⭐ (measured from base, bestie, don't forget the base)

πŸ’œ DESCRIPTION πŸ’œ

okay so real talk β€” note that this is OK as long as the pins are in a static array. like, that's the condition, that's the caveat, that's the whole tea. πŸ«– keep your pins static and you're slaying; don't, and, well… πŸ™ˆ the manpage says nothing else, so neither will I, periodt.


πŸ‘‘ SEE ALSO πŸ‘‘

the whole pinctrl-single.c friend group πŸ’… β€” this is the Kernel file ./drivers/pinctrl/pinctrl-single.c and everyone in it:

that's the whole squad fr fr πŸ”₯


πŸ’€ friendly reminder bestie: the "pins in a static array" thing is a real caveat, not just a vibe. it's in the DESCRIPTION for a reason, iykyk.

and that's the page! πŸŽ€ brought to you by ./drivers/pinctrl, dated October 2026 β€” mwah, love that for us πŸ’‹ see you in the next manpage, bestie πŸ¦‹πŸ’–

πŸ“¦ where this page comes from