devm_regulat...ter_notifier(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… devm_regulat...ter_notifier(9) β€” the Kernel API Manual one πŸŽ€

okay so bestie, you found the page for devm_regulator_register_notifier from the Kernel API Manual. it's a devres-flavoured lil wrapper and honestly it's giving "i set it up and the kernel cleans it up for me" main character energy ✨


🌸 NAME 🌸

devm_regulator_register_notifier β€” Resource managed regulator_register_notifier

like, the notifier registration, but with a babysitter. πŸ‘‘


✨ SYNOPSIS ✨

int devm_regulator_register_notifier (struct regulator *regulator ,
struct notifier_block *nb );

that's the whole signature, copy it exactly, do not @ me πŸ™ˆ


🫢 ARGUMENTS 🫢

  • regulator β€” regulator source πŸ’– (this is the regulator you're listening to)
  • nb β€” notifier block πŸ¦‹ (the thing that gets notified)

πŸ”₯ DESCRIPTION πŸ”₯

okay so here's the tea: the notifier will be registers under the consumer device, and it will automatically be unregistered when the source device is unbound. πŸŽ€

like literally, you don't have to do the cleanup yourself β€” devres handles it. no cap. that's the whole vibe. the wording in the original is literally "will be registers" and "automatically be unregistered", so bestie i'm telling you exactly what it says, grammar quirks and all πŸ’…


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/regulator/devres.c β€” go read the source, it's iconic ⭐


ngl the whole list is a whole friend group of devm_regulator_* functions and they all ate. πŸ“ go say hi to all of them.

and that's the page, bestie!! 🧚 from ./drivers/regulator, dated October 2026, and the manual section is still devm_regulat...ter_notifier(9) because some titles are just too long for their own good 😭 mwah πŸ’œ

πŸ“¦ where this page comes from