regulator_ge...limit_regmap(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ regulator_get_current_limit_regmap(9) ✨

okay bestie, welcome to the Kernel API Manual πŸ’… this one's a lil helper function from the regulator corner of the kernel and honestly? she's a time-saver. let's get into it 🫢


🌸 NAME 🌸

regulator_get_current_limit_regmap β€” the get_current_limit for regmap users, periodt ✨


πŸ¦‹ SYNOPSIS πŸ¦‹

int regulator_get_current_limit_regmap (struct regulator_dev *rdev );

πŸŽ€ ARGUMENTS πŸŽ€

  • rdev β€” the regulator you wanna operate on πŸ‘‘ like, this is the main character of the whole call, no cap.

πŸ’– DESCRIPTION πŸ’–

so here's the vibe 🌈 if your regulator uses regmap for its register I/O, you can just set the csel_reg and csel_mask fields in your descriptor, and then use this function as your get_current_limit operation. that's it. that's the whole thing. it saves some code πŸ’… and we love a low-effort high-reward situation, fr fr.

literally just point the operation at this bad boy and let her cook πŸ“

ngl, it's giving "why write it yourself when the kernel already wrote it for you" energy 😭 iconic behaviour tbh.

πŸ”₯ SEE ALSO πŸ”₯

the kernel file that lives with her 🧚:

  • ./drivers/regulator/helpers.c

and her whole friend group πŸ’œ (they all show up together, iykyk):


that's the whole page bestie, go forth and call your helpers πŸ’«

mwah πŸ’‹ this one came straight out of ./drivers/regulator, dated October 2026, and yes the header still says regulator_ge...limit_regmap(9) because truncation is her aesthetic apparently πŸ™ˆ stay slay, stay regulated ⭐
πŸ“¦ where this page comes from