regulator_get_regmap(9)

๐Ÿ“ฆ version 7.3.1, in nixpkgs unstable

๐Ÿฆ‹ regulator_get_regmap(9) ๐Ÿฆ‹

okay so this is the Kernel API Manual page for regulator_get_regmap(9), and yes, I folded the manual name in right here instead of copying that whole header line like a boring little robot. Weโ€™re doing this cute-style, bestie. ๐Ÿ’…

โœจ NAME โœจ

regulator_get_regmap โ€” gets the regulatorโ€™s register map. Thatโ€™s the vibe, thatโ€™s the whole assignment. Itโ€™s giving โ€œhand over the regmap for this regulatorโ€ energy, and honestly? obsessed. ๐Ÿ’–

๐ŸŒธ SYNOPSIS ๐ŸŒธ

The entire function shape is right here, no cap:

struct regmap * regulator_get_regmap (struct regulator *regulator );

๐ŸŽ€ ARGUMENTS ๐ŸŽ€

  • regulator โ€” regulator source. This is the regulator youโ€™re asking about; the manpage literally calls it the โ€œregulator source,โ€ so thatโ€™s the label weโ€™re keeping. ๐Ÿซถ

๐Ÿ’… RETURN ๐Ÿ’…

On the good path: a pointer to the struct regmap for regulator. Slay. โœจ

On the โ€œnot this one, bestieโ€ path: an ERR_PTR encoded -EOPNOTSUPP if regulator doesnโ€™t use regmap. No cap, thatโ€™s the whole return story. ๐Ÿ˜ญ

๐ŸŒˆ SEE ALSO ๐ŸŒˆ

The kernel file is ./drivers/regulator/core.c, and these legendary references are all in the group chat:


okay bye bestie ๐Ÿ’– โ€” this regulator_get_regmap(9) page is from ./drivers/regulator, dated October 2026. Thatโ€™s the footer, folded into a cute little sign-off. Mwah. ๐Ÿ’‹

๐Ÿ“ฆ where this page comes from