regulator_re...er_always_on(9)

💅 regulator_re...er_always_on — Kernel API Manual, section 9 🎀

okay bestie, buckle up, because this is the page for regulator_register_always_on from section 9 of the Kernel API Manual, and it's literally so niche but so important. it's giving "small helper, big job" energy fr fr 🦋

---

✨ NAME ✨

regulator_register_always_on — no cap, this one registers an always-on regulator and gives it a fixed name. that's the whole vibe. a regulator that is, like, always on. iconic 💅

---

🌸 SYNOPSIS 🌸

struct platform_device * regulator_register_always_on (int id , const char *name , struct regulator_consumer_supply *supplies , int num_supplies , int uv );

here's the whole signature, character for character, because we do not play about types in this house 🫶

---

🧚 ARGUMENTS 🧚

• id — the platform device id. it's the id, bestie. that's it, that's the whole thing 🎀
• name — the name you want the regulator to use. pick it, own it, slay ✨
• supplies — the consumers for this regulator. yep, the whole consumer situation lives here 💀
• num_supplies — how many consumers there are. literally just the count, keep it accurate 🙈
• uv — the voltage, measured in microvolts. microvolts!! tiny units, big energy ⚡

---

🔥 RETURN 🔥

you get back a pointer to the registered platform device — so good, so correct, main character energy 👑

or... NULL if memory allocation fails. which, like, we're manifesting it doesn't, but now you know 😭

---

🦋 SEE ALSO 🦋

• Kernel file ./drivers/regulator/fixed-helper.c — go read the source, iykyk, it's all there 🍓

---

and that's the page, bestie!! stay regulated, stay always-on, and don't forget to vibe check your memory allocations before you ship 💜🌈

source path: ./drivers/regulator · dated October 2026 · regulator_re...er_always_on(9) — mwah, catch you in the next manpage 🎀💖