STRUCT REGULATOR_CONSUMER_SUPPLY(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌈 struct regulator_consumer_supply(9) 🌈 β€” Kernel API Manual ✨

✨ NAME ✨

struct regulator_consumer_supply β€” the supply -> device mapping, no cap. Bestie, it's giving tiny-but-mighty lookup energy. 🫢

πŸ¦‹ SYNOPSIS πŸ¦‹

struct regulator_consumer_supply {
    const char *dev_name;
    const char *supply;
 };

πŸŽ€ Members πŸŽ€

  • dev_name β€” the result of dev_name for the consumer. That's literally the whole assignment, periodt. πŸ’…
  • supply β€” the name for the supply. Slay. ✨

🌸 Description 🌸

Okay so this maps a supply name to a device. The way that dev_name is used allows support for buses which make struct device available late β€” such as I2C. Iconic behavior, honestly. πŸ’–

πŸ‘‘ SEE ALSO πŸ‘‘

  • Kernel file ./include/linux/regulator/machine.h β€” plus these struct besties: struct regulator_state(9), struct regulation_constraints(9), and struct regulator_init_data(9). πŸ¦‹

mwah πŸ’‹ β€” source/version: ./include/linux/regulator, dated October 2026; page: struct regul...sumer_supply(9). That's the footer, bestie β€” no cap. πŸŽ€

πŸ“¦ where this page comes from