pf9453_regul...delay_regmap(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… pf9453_regul...delay_regmap(9) β€” the Kernel API Manual, bestie edition

okay so this is a page from the Kernel API Manual (yes, the manual name is literally pf9453_regul...delay_regmap(9), they truncated it with dots, iconic of them honestly) and today we're learning about ramp delays. stay with me, it's actually cute πŸŽ€


✨ NAME ✨

pf9453_regulator_set_ramp_delay_regmap β€” set the ramp delay, but make it for the regmap girlies πŸ’–


🌸 SYNOPSIS 🌸

int pf9453_regulator_set_ramp_delay_regmap (struct regulator_dev *rdev ,
int ramp_delay );

like, that's the whole signature. two args. no drama. πŸ¦‹


🫢 ARGUMENTS 🫢

  • rdev β€” the regulator we're operating on. it's the regulator. main character energy, obviously πŸ‘‘
  • ramp_delay β€” the desired ramp delay value, in microseconds. yes, microseconds, not milliseconds, do not come for me πŸ™ˆ

πŸ’… DESCRIPTION πŸ’…

so here's the vibe: regulators that use regmap for their register I/O can just set the ramp_reg and ramp_mask fields in their descriptor, and then use this function as their set_ramp_delay operation. that's it. that's the whole flex. it saves you some code, which is honestly such a slay ✨

lowkey the whole point is you don't have to write your own ramp delay handler. the descriptor fields do the work, this function shows up, does its thing, leaves. periodt. πŸ’€

πŸ”₯ RETURN πŸ”₯

0 on success, or a negative errno if things went sideways. so like, check it. don't just assume. ngl 😭


🌈 SEE ALSO 🌈

all the regmap siblings, fr fr 🧚


and that's the page!! mwah πŸ’œ it lives over in ./drivers/regulator, dated October 2026, and answers to the name pf9453_regul...delay_regmap(9) β€” ok bye bestie, go set some ramp delays πŸŽ€β­

πŸ“¦ where this page comes from