pcs_add_function(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pcs_add_function(9) β€” like, the whole vibe

okay so first things first, bestie: this is from the Kernel API Manual, and it's about pcs_add_function β€” the little guy that adds a new function to the function list. yes that's literally the whole plot. no cap. πŸŽ€


✨ NAME ✨

pcs_add_function β€” adds a new function to the function list πŸ¦‹


🌸 SYNOPSIS 🌸

int pcs_add_function (struct pcs_device *pcs , struct pcs_function **fcn
, const char *name , struct pcs_func_vals *vals , unsigned int nvals ,
const char **pgnames , unsigned int npgnames );

like, seven whole arguments. she's high maintenance and we love her for it πŸ’…


🫢 ARGUMENTS 🫢

  • pcs β€” the pcs driver instance. the main character of this whole operation πŸ‘‘
  • fcn β€” the new function, allocated. this is where your freshly-made baby ends up ✨
  • name β€” name of the function. give her a good one, iykyk πŸŽ€
  • vals β€” array of mux register value pairs used by the function. the actual guts of the thing πŸ”₯
  • nvals β€” number of mux register value pairs. yes bestie, count them, all of them πŸ’œ
  • pgnames β€” array of pingroup names for the function. friend group energy fr fr 🌈
  • npgnames β€” number of pingroup names. count those too πŸ™ˆ

πŸ’€ DESCRIPTION πŸ’€

the actual description is one (1) sentence and it's giving "professor who ran out of time":

Caller must take care of locking.

that's it. that's the whole thing. no locking, no safety β€” this function does not hold your hand, bestie. you want it locked, you lock it. not me, not the kernel, you. 😭


🧚 SEE ALSO 🧚

kernel file: ./drivers/pinctrl/pinctrl-single.c

and the whole extended friend group, because she does not go ANYWHERE alone:

that's twenty-five entries. yes i counted. someone had to. πŸ“


mwah πŸ’‹ this page lives in ./drivers/pinctrl, dated October 2026 β€” bookmark it, screenshot it, put it on your fridge. periodt. ⭐

πŸ“¦ where this page comes from