regulator_m...tage_iterate(9)

📦 version 7.3.1, in nixpkgs unstable

💖 regulator_m...tage_iterate(9) — a Kernel API Manual moment ✨

okay so first of all, bestie, this page lives in the Kernel API Manual, and the function it's hyping up is regulator_map_voltage_iterate — yes the title is literally truncated to regulator_m...tage_iterate(9) and no we are not fixing it, that's just how it's filed 💅

🌸 NAME 🌸

regulator_map_voltage_iterate — lowkey map_voltage() but built on top of list_voltage(), and honestly? it eats 🍓

✨ SYNOPSIS ✨

int regulator_map_voltage_iterate (struct regulator_dev *rdev , int
       min_uV , int max_uV );

three args, one int coming back at you, no drama 🎀

🦋 ARGUMENTS 🦋

  • rdev — the regulator we're operating on, the main character of this whole function ngl 👑
  • min_uV — the lower bound for the voltage, like the floor of the vibe 🌸
  • max_uV — the upper bound for the voltage, the ceiling, the limit, the boundary bestie 💀

🧚 DESCRIPTION 🧚

okay so picture this: you're a driver implementing set_voltage_sel and list_voltage, and you need a map_voltage operation. congrats, this is literally the one for you 🫶

what it does is call list_voltage over and over — like, keep going, girl — until it lands on something in bounds for the voltages you asked for. that's it. that's the whole strategy. iterative queen behaviour, no cap ⭐

fr fr if you're the set_voltage_sel + list_voltage combo type, this is your map_voltage. it just keeps poking list_voltage until something falls inside the requested range 💖

🌈 SEE ALSO 🌈

the whole friend group, in order, exactly as listed, because we don't leave anyone out:

and that's the page, bestie 🎀 this little number hangs out under ./drivers/regulator and it's dated October 2026 — iykyk, go read the others, mwah 💜🦋✨

📦 where this page comes from