STRUCT TEGRA_PINCTRL_SOC_DATA(9)
๐ struct tegra_pinctrl_soc_data(9) โ Kernel API Manual ๐
okay bestie, welcome to the glow-up doc for struct tegra_pinctrl_soc_data โ it's the config blueprint for the Tegra pin controller driver, and honestly? it's giving "quietly runs the whole show" energy ๐
โจ NAME โจ
struct tegra_pinctrl_soc_data โ the Tegra pin controller driver configuration ๐ฆ
๐ธ SYNOPSIS ๐ธ
struct tegra_pinctrl_soc_data {
unsigned ngpios;
const char *gpio_compatible;
const struct pinctrl_pin_desc *pins;
unsigned npins;
const char * const *functions;
unsigned nfunctions;
const struct tegra_pingroup *groups;
unsigned ngroups;
bool hsm_in_mux;
bool schmitt_in_mux;
bool drvtype_in_mux;
bool sfsel_in_mux;
};
like, look at her. every field accounted for, no notes ๐
๐ Members ๐
ngpiosโ how many GPIO pins the pin controller HW actually touches. the headcount, basically ๐งฎgpio_compatibleโ the device-tree GPIO compatible string. her official government name โจpinsโ an array describing all the pins the pin controller affects. โ ๏ธ and here's the rule, no cap: all pins which are also GPIOs must be listed first within the array, and be numbered identically to the GPIO controller's numbering. so like, order matters, bestie. don't be chaotic with it ๐ซถnpinsโ the number of entries inpins. the count ๐ธfunctionsโ an array describing all the mux functions the SoC supports. the whole menu ๐nfunctionsโ the number of entries infunctions. menu length, fr fr ๐ขgroupsโ an array describing all the pin groups the pin SoC supports. squad goals, grouped up ๐ฏngroupsโ the number of entries ingroups. how many squads ๐hsm_in_muxโ High-speed mode field. ๐จ only applicable to devices with one pin per group. read that twice if you need to ๐schmitt_in_muxโ Schmitt trigger field. ๐ญ same deal: only applicable to devices with one pin per group.drvtype_in_muxโ Drivetype field. ๐ฅ again โ only applicable to devices with one pin per group.sfsel_in_muxโ Special function selection field. โญ and yep, only applicable to devices with one pin per group. the four*_in_muxbooleans are all matching, it's giving coordinated outfit ๐
lowkey important: those last four are only for devices with one pin per group. not a vibe check you get to skip ๐
๐ฆ SEE ALSO ๐ฆ
- Kernel file
./drivers/pinctrl/tegra/pinctrl-tegra.hstructtegra_function(9), structtegra_pingroup(9)โ go read the whole family, iykyk ๐
and that's the page!! ๐ this masterpiece lives at ./drivers/pinctrl/tegra, dated October 2026 โ so she's serving main character energy from the future, and honestly? obsessed. slay, periodt, go configure some pins ๐โจ๐ซถ
๐ฆ 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