regulator_bulk_enable(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… regulator_bulk_enable(9) πŸ’…

okay bestie, welcome to the Kernel API Manual entry for regulator_bulk_enable β€” yes it's a real manual page, yes it's a C function, no you can't skip it, it's literally on the syllabus πŸŽ€


✨ NAME ✨

regulator_bulk_enable β€” enable multiple regulator consumers, like, all at once, main character energy only πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

int regulator_bulk_enable (int num_consumers , struct
       regulator_bulk_data *consumers );

that's it. that's the whole signature. no cap. 🫢


🌸 ARGUMENTS 🌸

  • num_consumers β€” the number of consumers. like, how many of them there are. count them. ✨
  • consumers β€” the consumer data; clients are stored here. this is where all your little consumer besties live. πŸŽ€

πŸ’– DESCRIPTION πŸ’–

okay so this convenience API lets consumers enable multiple regulator clients in a single API call. one call. not ten. not a for-loop you wrote at 3am. one. πŸ”₯

and here's the icon behaviour ngl: if any consumers cannot be enabled then any others that were enabled will be disabled again prior to return. it's giving "we go up together or nobody goes up" 😭 the way it cleans up after itself before it even returns… obsessed. πŸ’…


⭐ RETURN ⭐

0 on success, or a negative error number on failure. that's the vibe check. if you get 0 you ate. if you get negative, bestie, something went off. 😭


🌈 SEE ALSO 🌈

Kernel file ./drivers/regulator/core.c β€” and literally the entire extended family, because nothing in this subsystem is an only child:

like I said. whole family reunion. πŸ§šπŸ’œ


friendly reminder from your local unix girlie: this whole page comes from ./drivers/regulator, dated October 2026, and yes it's still filed under regulator_bulk_enable(9) β€” so if you cite it, cite it cute. πŸ“βœ¨
πŸ“¦ where this page comes from