devm_regulat...et_exclusive(9)
β¨ devm_regulator_get_exclusive(9) β¨
okay bestie, buckle up β this one lives in the Kernel API Manual (the devm_regulat...et_exclusive(9) page, yes the title is truncated like that, we love a mysterious queen π
) and it's all about grabbing a regulator exclusively and having the kernel clean up after you like the responsible main character it is π«Ά
πΈ NAME πΈ
devm_regulator_get_exclusive β it's the resource-managed glow-up of regulator_get_exclusive(), literally the same energy but with automatic cleanup β¨
π SYNOPSIS π
struct regulator * devm_regulator_get_exclusive (struct device *dev ,
const char *id );
no cap, that's the whole signature β two args, one pointer out π
π¦ ARGUMENTS π¦
devβ the device that's gonna be supplied. it's giving "who's getting the power" πidβ the supply name or the regulator ID. you get to pick which flavor of naming, iykyk π
β DESCRIPTION β
so this is the managed version of regulator_get_exclusive. and what "managed" means here is the iconic part: any regulator you get back from this function gets automatically regulator_put'd when the driver detaches ππ«Ά no manual cleanup era, no leaks, we simply do not stress about it.
ngl if you want the full lore, go read regulator_get for more information β that's where the real details live, fr fr π
π SEE ALSO π
the kernel file is ./drivers/regulator/devres.c β that's the home base π
and here's the whole friend group, all of them (9) pages, all of them tagged along for the ride:
devm_regulator_get(9)devm_regulator_get_enable_optional(9)devm_regulator_get_enable(9)devm_regulator_get_optional(9)devm_regulator_get_enable_read_voltage(9)devm_regulator_put(9)devm_regulator_bulk_get(9)devm_regulator_bulk_get_exclusive(9)devm_regulator_bulk_get_const(9)devm_regulator_bulk_put(9)devm_regulator_bulk_get_enable(9)devm_regulator_register(9)devm_regulator_register_supply_alias(9)devm_regulator_bulk_register_supply_alias(9)devm_regulator_register_notifier(9)devm_regulator_unregister_notifier(9)devm_regulator_irq_helper(9)devm_of_regulator_get(9)devm_of_regulator_get_optional(9)
like, that's a whole squad. the bulk ones? the alias ones? the notifier ones? obsessed π
π reminder bestie: the "exclusive" in the name is doing real work here β it's not just a cute adjective, it's the whole point of the call. don't go thinking you can swap it out for the plain devm_regulator_get and get the same behavior, because that's not what the page says and we don't make stuff up in this house π
and that's the page!! signing off with the deets: this manual lives under ./drivers/regulator, dated October 2026, and the footer reads devm_regulat...et_exclusive(9) β same mysterious truncated title energy as the top, we stan a consistent brand πΈβ¨π
π¦ 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