regulator_ma...linear_range(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 regulator_map_voltage_linear_range β€” the kernel API manual page, bestie edition 🌸

okay so this is regulator_ma...linear_range(9) from the Kernel API Manual β€” literally the glow-up guide for regulator_map_voltage_linear_range. stay with me, it's cute and it's important πŸ’…


✨ NAME ✨

regulator_map_voltage_linear_range β€” it's map_voltage() but make it multiple linear ranges. iconic behaviour only πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

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

that's the whole signature, no notes, chef's kiss ✨


πŸ’– ARGUMENTS πŸ’–

  • rdev β€” the regulator we're operating on. the main character of this whole situation πŸ‘‘
  • min_uV β€” the lower bound for voltage. the floor, the bare minimum, the "i will not be accepting less" 🌸
  • max_uV β€” the upper bound for voltage. the ceiling, the limit, the "don't push it" 🫢

⭐ DESCRIPTION ⭐

so if you're a driver and you've got linear_ranges chillin' in your descriptor? you can literally use this as your map_voltage callback. that's it, that's the whole vibe. no cap πŸ”₯

it's giving "drop-in replacement, zero drama" and honestly? we love that for you πŸ’œ


🌈 SEE ALSO 🌈

the kernel file lives at ./drivers/regulator/helpers.c β€” go say hi 🧚

and now the friendship circle, the whole group chat, everyone's invited:

periodt. that's the list, every single one, don't skip a single bestie πŸ’€πŸ’–


ngl this page is short but it's mighty β€” if you're writing a regulator driver with linear_ranges in the descriptor, this callback is the one. slay πŸ¦‹

kisses and a little sign-off: this one's straight out of the kernel source tree at ./drivers/regulator, dated October 2026, and yeah β€” the page is regulator_ma...linear_range(9), same as it ever was. ily, go map some voltages πŸ’…πŸŽ€β­

πŸ“¦ where this page comes from