regulator_is_enabled(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– regulator_is_enabled(9) πŸ’–

okay bestie, welcome to the Kernel API Manual glow-up for regulator_is_enabled(9) β€” the β€œis the regulator output enabled” vibe check. it’s giving tiny-but-mighty kernel energy, and we’re obsessed. 🫢✨


✨ NAME ✨

regulator_is_enabled β€” is the regulator output enabled πŸ’…

🌸 SYNOPSIS 🌸

int regulator_is_enabled (struct regulator *regulator );

πŸŽ€ ARGUMENTS πŸŽ€

  • regulator β€” regulator source. that’s the one and only argument, bestie. πŸŽ€

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so listen: the device backing this regulator handle can have multiple users. that means it might be enabled even if regulator_enable was never called for this particular source. so don’t come for this function’s wig when another user already turned it on β€” it’s not lying, it’s just not keeping a private diary for your source only. 😭✨

πŸ’… RETURN πŸ’…

  • Positive β€” the regulator driver backing the source/client has requested that the device be enabled. πŸ’–
  • Zero β€” it hasn’t. 🫢
  • Else a negative error number β€” yep, that’s the error vibe. πŸ’€

🌈 SEE ALSO 🌈

Kernel file: ./drivers/regulator/core.c

and now the whole bestie squad of regulator-adjacent functions, no cap:


mwah πŸ’‹ β€” this page is brought to you by the Kernel API Manual, sourced from ./drivers/regulator and dated October 2026, all for regulator_is_enabled(9). periodt. βœ¨πŸŽ€

πŸ“¦ where this page comes from