sppctl_fully_pinmux_conv(9)
π NAME π
sppctl_fully_pinmux_conv β okay so this one converts a GPIO number into a fully-pinmux control-field setting. That's literally the whole gig, bestie β¨
This page lives in the Kernel API Manual section (9), so yes, it's a kernel-internal function, not something you type into your shell π«Ά
β¨ SYNOPSIS β¨
int sppctl_fully_pinmux_conv (unsigned int offset );
π ARGUMENTS π
offsetβ ngl, the original page is out here giving us nothing: it's marked-- undescribed --. No cap, that's all we get π (So don't come for me, I'm just the messenger π)
πΈ DESCRIPTION πΈ
Okay so here's the tea β β every fully-pinmux function can be mapped to any of GPIO 8 ~ 71 by setting its control-field. Say it with me: any of GPIO 8 through 71 π
Peep the table below for the control-field β GPIO mapping, iykyk:
control-field | GPIO
--------------+--------
0 | No map
1 | 8
2 | 9
3 | 10
: | :
65 | 71
So control-field 0 is the "No map" girlie (she's not mapped to anything, she's just vibing), 1 gives you GPIO 8, 2 gives you GPIO 9, 3 gives you GPIO 10, the : rows are the continuation of that whole situation, and control-field 65 lands you all the way at GPIO 71. Slay, that's the range π₯
π¦ SEE ALSO π¦
- The kernel file
./drivers/pinctrl/sunplus/sppctl.cβ that's the main character right there π sppctl_func_set(9)sppctl_gmx_set(9)sppctl_first_get(9)sppctl_master_get(9)
Bestie reminder: this page is short short. If you need the actual behaviour deets, go read ./drivers/pinctrl/sunplus/sppctl.c β it's giving "the source is the documentation" energy π
π And that's a wrap! This page comes to you straight outta ./drivers/pinctrl/sunplus, dated October 2026, and it's filed under sppctl_fully_pinmux_conv(9) β periodt, go forth and pinmux responsibly π§π
π¦ 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