_store_optimized_voltages(9)

✨ _store_optimized_voltages(9) ✨

okay so bestie, welcome to the Kernel API Manual 💅 this one's a little function living its best life in the kernel, and honestly? it's giving "quietly important." let's get into it 🫶

---

🌸 NAME 🌸

_store_optimized_voltages — store optimized voltages 🔥

like, the whole name is literally the job. no cap.

---

🎀 SYNOPSIS 🎀

int _store_optimized_voltages (struct device *dev , struct
ti_opp_supply_data *data );

two args, one int coming back at ya. that's the whole vibe ✨

---

🦋 ARGUMENTS 🦋

• dev — the ti opp supply device for which we need to store info, iykyk. it's the device in question, the main character of this call 👑
• data — data specific to the device 💜 like, the device's own lil info bundle

---

🌈 DESCRIPTION 🌈

so what does it actually do? it picks up efuse based optimized voltages for VDD that are unique per device 🧚 and then it stores them in an internal data structure so they're ready to go during transition requests. literally prepping ahead of time, which is such a slay of a design honestly ✨

per-device voltages >>> one-size-fits-all voltages, fr fr 💅

---

⭐ RETURN ⭐

if it works? 0 🎉 iconic, flawless, no notes.

otherwise it hands back the appropriate error value 😭 so like, check your return value bestie, don't just assume.

---

💖 SEE ALSO 💖

kernel file ./drivers/opp/ti-opp-supply.c — and the whole friend group:

• struct ti_opp_supply_optimum_voltage_table(9)
• struct ti_opp_supply_data(9)
• struct ti_opp_supply_of_data(9)
• _free_optimized_voltages(9)
• _get_optimal_vdd_voltage(9)

go read them, they're all connected, it's a whole ecosystem 💀🌸

---

heads up bestie: everything above lives in ./drivers/opp — that's the source/version situation — and this page is dated October 2026, so mark your calendar 🎀

and that's the page!! _store_optimized_voltages(9), done and dusted, ate and left no crumbs 👑💜