STRUCT GPIO_REGULATOR_CONFIG(9)
π struct gpio_regulator_config(9) π
okay so bestie, welcome to the Kernel API Manual entry for struct gpio_regulator_config β yes that's the real title, the header up there gets truncated to struct gpio_...lator_config(9) because even the manpage renderer runs out of breath π«Ά
β¨ NAME β¨
struct gpio_regulator_config β the config structure. that's it, that's the whole name. it's giving "I contain multitudes but my name is literally just config structure" π
π¦ SYNOPSIS π¦
here's the whole struct, copied exactly, no cap:
struct gpio_regulator_config {
const char *supply_name;
const char *input_supply;
unsigned enabled_at_boot:1;
unsigned startup_delay;
enum gpiod_flags *gflags;
int ngpios;
struct gpio_regulator_state *states;
int nr_states;
enum regulator_type type;
struct regulator_init_data *init_data;
};
look at her. ten whole members. main character energy fr fr π
π Members π
supply_name
Name of the regulator supply. that's her name, that's her whole identity β¨
input_supply
Name of the input regulator supply. the supply that feeds the supply, iykyk πΈ
enabled_at_boot
Whether the regulator has been enabled at boot or not. 1 = Yes, 0 = No. this is used to keep the regulator at the default state π
ngl this one is a 1-bit field so it's living its best tiny life. be nice to her.
startup_delay
Start-up time in microseconds. literally the "give me a sec" of the regulator world π
gflags
Array of GPIO configuration flags for initial states. plural flags, plural states, we love an array π¦
ngpios
Number of GPIOs and configurations available. count 'em, bestie π₯
states
Array of gpio_regulator_state entries describing the gpio state for specific voltages. this is where the voltage-to-gpio lore lives π
nr_states
Number of states available. the states array said "how many of me are there" and this field answered π
init_data
regulator_init_data. that's the whole description. short, sweet, iconic, no notes π
π Description π
okay so this structure contains gpio-voltage regulator configuration information that must be passed by platform code to the gpio-voltage regulator driver. must. not "should", not "maybe if you feel like it" β the platform code has to hand it over, periodt π
think of it as the little care package π that platform code packs up so the gpio-voltage regulator driver knows what it's working with. without it the driver is just standing there like π§
β SEE ALSO β
- Kernel file
./include/linux/regulator/gpio-regulator.h struct gpio_regulator_state(9)β go read her too, she's the other half of this story π
and that's the whole vibe check, bestie π«Ά this page came from ./include/linux/regulator, dated October 2026, and the footer still insists on calling her struct gpio_...lator_config(9) β we stan a consistent queen π
β¨
π¦ 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