of_regulator_dev_lookup(9)

📦 version 7.3.1, in nixpkgs unstable

👑 of_regulator_dev_lookup(9) 👑

okay so bestie, this is the Kernel API Manual page for of_regulator_dev_lookup(9), and it's here to spill the tea on looking up a regulator device using device tree only. No extra sources, no side quests — just device tree vibes. ✨

💖 NAME 💖

of_regulator_dev_lookup — lookup a regulator device with device tree only.

✨ SYNOPSIS ✨

struct regulator_dev * of_regulator_dev_lookup (struct device *dev , struct device_node *np , const char *supply );

🎀 ARGUMENTS 🎀

  • dev — Device pointer for regulator supply lookup. Like, the device bestie you're checking for a supply. 🫶
  • np — Device node pointer for regulator supply lookup. The device-node bestie in the mix. 🦋
  • supply — Supply name or regulator ID. This is the name/ID you're hunting for, periodt. 💅

🔥 RETURN 🔥

On success, you get a pointer to the struct regulator_dev — iconic. On error, you get an ERR_PTR encoded value. That's the whole return vibe. 💀

🦋 DESCRIPTION 🦋

If it succeeds, it returns a pointer to the struct regulator_dev that corresponds to the name supply, and the embedded struct device refcount is incremented by one. ✨ The refcount must be dropped by calling put_device. No cap, don't forget that part — it's important. 🫶

On failure, one of these ERR_PTR encoded values comes back:

  • -ENODEV if lookup fails permanently. It's giving "nope, not happening, ever." 💀
  • -EPROBE_DEFER if lookup could succeed in the future. It's giving "not right now bestie, maybe later." ⏳

🌈 SEE ALSO 🌈

Kernel file: ./drivers/regulator/of_regulator.c

xoxo bestie 💅 this of_regulator_dev_lookup(9) page's source/version is ./drivers/regulator, and it's dated October 2026. slay. 🎀

📦 where this page comes from