devm_gpio_regmap_register(9)
π devm_gpio_regmap_register(9) π
okay so welcome to the Kernel API Manual, bestie β we're talking about devm_gpio_regmap_register(9) today and it's literally the resource-managed version of gpio_regmap_register(). slay.
β¨ NAME β¨
devm_gpio_regmap_register β it's the resource-managed glow-up of gpio_regmap_register(), periodt.
π SYNOPSIS π
struct gpio_regmap * devm_gpio_regmap_register (struct device *dev ,
const struct gpio_regmap_config *config );
π¦ ARGUMENTS π¦
devβ the device that is registering this GPIO device. it's giving "main character device energy" πconfigβ the configuration forgpio_regmap. yes bestie, this is where the setup lives π
πΈ DESCRIPTION πΈ
so this is the managed gpio_regmap_register. for a generic regmap GPIO device registered by this function, gpio_regmap_unregister is automatically called on driver detach. no cap β the cleanup is handled for you, automatic style. β¨
if you want more info, go see gpio_regmap_register β it's the non-managed sibling and it has the details. π«Ά
π₯ RETURN π₯
it returns a pointer to the registered gpio_regmap β iconic β or an ERR_PTR error value if things go sideways. π
π SEE ALSO π
- the kernel file
./drivers/gpio/gpio-regmap.c gpio_regmap_register(9)gpio_regmap_unregister(9)
π cute little sign-off: this page is from./drivers/gpio, dated October 2026, and it's the manual fordevm_gpio_regmap_register(9). bye bestie, go register some GPIOs 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