STRUCT PCS_GPIOFUNC_RANGE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ‘‘ struct pcs_gpiofunc_range(9) β€” the kernel api manual bestie πŸ’…

okay so welcome to the Kernel API Manual entry for struct pcs_gpiofunc_range(9) β€” literally the glow-up you needed for understanding pin ranges that share the same mux value of gpio function. no cap, this one's a little icon. ✨


🌸 NAME 🌸

struct pcs_gpiofunc_range β€” pin ranges with same mux value of gpio function. it's giving "group chat for pins that all picked the same vibe." πŸŽ€


✨ SYNOPSIS ✨

here's the whole struct, copied exactly because we do not play with code integrity in this house:

struct pcs_gpiofunc_range {
    unsigned offset;
    unsigned npins;
    unsigned gpiofunc;
    struct list_head node;
 };

πŸ’– Members πŸ’–

  • offset β€” offset base of pins. think of it as where this little pin party starts. πŸ“
  • npins β€” number pins with the same mux value of gpio function. yes bestie, it's the headcount for the function-matching squad. πŸ‘―β€β™€οΈ
  • gpiofunc β€” mux value of gpio function. the actual vibe/mux setting they all share. πŸ”₯
  • node β€” list node. the link that keeps this struct connected to the rest of the list, lowkey main character energy for data structure cohesion. πŸ”—

πŸ¦‹ SEE ALSO πŸ¦‹

kernel file ./drivers/pinctrl/pinctrl-single.c and all its friends β€” literally the whole pinctrl-single fam. go say hi:


πŸ’€ reminder: this is kernel API territory, so keep your structs and your references exactly as they are β€” no renaming, no merging, no invented options. facts stay facts, even when the vibe is immaculate. 🫢

okay that's the whole page, bestie β€” sourced from ./drivers/pinctrl, Kernel API Manual, dated October 2026, and it's struct pcs_gpiofunc_range(9) all the way down. slay, study, and cite your kernel docs responsibly. πŸ’œπŸŒˆβ­

πŸ“¦ where this page comes from