of_regulator_get_optional(9)

💜 of_regulator_get_optional ✨

okay so you're reading the Kernel API Manual page for of_regulator_get_optional(9) — yes bestie, the optional one, the one that's chill about things not existing 🫶

---

🌸 NAME 🌸

of_regulator_get_optional — grab an optional regulator via device tree lookup. lowkey the whole personality of this function is "if it's not there, that's fine, no drama" 💅

---

✨ SYNOPSIS ✨

struct regulator * of_regulator_get_optional (struct device *dev ,
struct device_node *node , const char *id );

---

🎀 ARGUMENTS 🎀

• dev — the device, used for dev_printk messages. it's the one doing the talking 📢
• node — the device node for the regulator's "consumer". the consumer being whoever's asking for the supply, iykyk
• id — the supply name

---

🦋 RETURN 🦋

a pointer to struct regulator corresponding to the regulator producer ⭐ — or, if things went sideways, a PTR_ERR encoded error number. so like, check it with IS_ERR() before you go dereferencing, bestie, fr fr 😭

---

💖 DESCRIPTION 💖

this one is intended for consumers that want to get a regulator supply directly from a device node, and that can and want to deal with the absence of such supplies. main character energy: independent, self-sufficient, unbothered 🌈

heads up though: this will _not_ consider supply aliases. not even a little. nope 🙈

see regulator_dev_lookup for the actual lookup business.

---

🌟 SEE ALSO 🌟

• Kernel file ./drivers/regulator/of_regulator.c
• of_get_regulator_init_data(9)
• of_regulator_match(9)
• of_get_child_regulator(9)
• of_get_regulator(9)
• of_regulator_dev_lookup(9)
• of_regulator_get(9)
• of_check_coupling_data(9)
• of_parse_coupled_regulator(9)
• of_regulator_bulk_get_all(9)

go read them all, they're iconic, the whole squad 👑

---

and that's the whole page, bestie 💜 this one lives in ./drivers/regulator, it's from the Kernel API Manual, dated October 2026 — slay, go get your optional regulator, and remember: absence is a valid outcome 🎀✨