ufshcd_parse_regulator_info(9)

✨ ufshcd_parse_regulator_info ✨

okay bestie, so this is a page from the Kernel API Manual for ufshcd_parse_regulator_info(9) — yes it's a function, yes it's got a (9) after it, that's just how kernel docs roll, don't worry about it 💅

---

🌸 NAME 🌸

ufshcd_parse_regulator_info — literally just: go get the regulator info from the device tree 🎀

---

🦋 SYNOPSIS 🦋

int ufshcd_parse_regulator_info (struct ufs_hba *hba );

---

💖 ARGUMENTS 💖

• hba — the per adapter instance. that's it. that's the whole argument. it's giving "one job, one parameter" and honestly? iconic. 👑

---

🌈 DESCRIPTION 🌈

so what this does is grab the regulator info from the device tree for the vcc, vccq, and vccq2 power supplies. those three. all of them. no cap. ⚡

now here's the important bit, bestie, so like, listen up 🫶 — if any of those supplies are not defined, then the code assumes they're always-on, and it returns zero. like, "oh you didn't mention it? cool, it's just always on then, no notes." 💀

but!! if the property is defined and the parsing fails, then it returns the corresponding error. so defined-but-broken is not a vibe, and it will absolutely tell you about it. 😭

---

⭐ RETURN ⭐

• 0 upon success 🎉
• < 0 upon failure 😔

---

👑 SEE ALSO 👑

• Kernel file ./drivers/ufs/host/ufshcd-pltfrm.c — the source, the mothership, the main character 💅
• ufshcd_parse_tx_eq_settings_for_gear(9)
• ufshcd_parse_clock_min_max_freq(9)
• ufshcd_negotiate_pwr_params(9)
• ufshcd_parse_gear_limits(9)
• ufshcd_pltfrm_init(9)
• ufshcd_pltfrm_remove(9)

all the siblings, all referenced, all present and accounted for 🧚

---

that's the whole page, bestie 💜 — brought to you from ./drivers/ufs/host, dated October 2026, and yes it's still ufshcd_parse_regulator_info(9) at the bottom, we love a consistent footer 🍓✨