devm_regula...et_exclusive(9)

📦 version 7.3.1, in nixpkgs unstable

💅 devm_regula...et_exclusive(9) — like, the full name is devm_regulator_bulk_get_exclusive

okay so bestie, welcome to the Kernel API Manual 🎀 (yes the header truncates the name, that's just how it vibes — the real one is devm_regulator_bulk_get_exclusive).

✨ NAME ✨

devm_regulator_bulk_get_exclusive — managed exclusive get of multiple regulator consumers. it's giving "grab the whole friend group at once, and they get auto-released later" 🫶

🌸 SYNOPSIS 🌸

int devm_regulator_bulk_get_exclusive (struct device *dev , int
num_consumers , struct regulator_bulk_data *consumers );

🦋 ARGUMENTS 🦋

  • dev — the device to supply. literally the main character here 🔥
  • num_consumers — how many consumers to register. count 'em, bestie.
  • consumers — the configuration of consumers; the clients get stored here. this is where the good stuff lands 💖

👑 DESCRIPTION 👑

so it returns 0 on success, and a negative error number on failure. periodt.

this helper function lets drivers exclusively get several regulator consumers in one single operation, with management baked in — the regulators will automatically be freed when the device is unbound ✨. that's the "managed" part, iykyk.

and listen: if ANY of the regulators can't be acquired, then any regulators that were already allocated will be freed before returning to the caller. no leaks, no leftover mess, she cleans up after herself 💅

🌈 SEE ALSO 🌈

okay that's the whole page bestie, go read the source, it ate 💀✨

sign-off time: this lil masterpiece lives in ./drivers/regulator, dated October 2026, and the manual name on the tin is Kernel API Manual 🌸 mwah, bye 🎀

📦 where this page comes from