regulator_bu...supply_alias(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… regulator_bulk_register_supply_alias β€” register multiple aliases, bestie

okay so this page is from the Kernel API Manual, and the function name got a little truncated in the header (regulator_bu...supply_alias(9)) but like, we know who she is. it's giving "long name, big responsibility" ✨


🌸 SYNOPSIS 🌸

int regulator_bulk_register_supply_alias (struct device *dev , const
char *const *id , struct device *alias_dev , const char *const *alias_id
, int num_id );

literally the whole signature, character for character, no cap 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • dev β€” the device that's gonna be handed the regulator "consumer" role. main character energy fr.
  • id β€” a List of supply names or regulator IDs. plural vibes.
  • alias_dev β€” the device that should actually be used to look up the supply πŸ‘€
  • alias_id β€” a List of supply names or regulator IDs that should be used to look up the supply
  • num_id β€” how many aliases we're registering. the count. the quantity. the amount. πŸ’…

✨ DESCRIPTION ✨

so this helper function is the ultimate group-project glitch: it lets drivers register several supply aliases in one operation. one shot, all the aliases. iconic πŸ¦‹

but here's the tea β€” if any of the aliases can't be registered, then any aliases that were already registered get removed before it returns to the caller. it's a full rollback, bestie, no half-finished situationship allowed. 😭

🌈 RETURN 🌈

0 on success, or a negative error number on failure. that's it. that's the whole vibe check ⭐


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/regulator/core.c, plus honestly the entire extended universe of regulator functions β€” we're listing them all, don't come for me:

regulator_lock_nested(9), regulator_lock(9), regulator_unlock(9), regulator_lock_two(9), regulator_unlock_two(9), regulator_unlock_dependent(9), regulator_lock_dependent(9), set_machine_constraints(9), regulator_event_work_fn(9), regulator_event_forward_notifier(9), register_regulator_event_forwarding(9), set_supply(9), set_consumer_device_supply(9), regulator_dev_lookup(9), _regulator_get_common(9), regulator_get(9), regulator_get_exclusive(9), regulator_get_optional(9), regulator_put(9), regulator_register_supply_alias(9), regulator_unregister_supply_alias(9), regulator_bulk_unregister_supply_alias(9), regulator_ena_gpio_ctrl(9), _regulator_check_status_enabled(9), _regulator_handle_consumer_enable(9), _regulator_handle_consumer_disable(9), regulator_enable(9), regulator_disable(9), regulator_force_disable(9), regulator_disable_deferred(9), regulator_is_enabled(9), regulator_count_voltages(9), regulator_list_voltage(9), regulator_get_regmap(9), regulator_get_hardware_vsel_register(9), regulator_list_hardware_vsel(9), regulator_hardware_enable(9), regulator_get_linear_step(9), regulator_is_supported_voltage(9), regulator_set_voltage(9), regulator_set_voltage_time(9), regulator_set_voltage_time_sel(9), regulator_sync_voltage(9), regulator_get_voltage(9), regulator_set_current_limit(9), regulator_get_current_limit(9), regulator_get_unclaimed_power_budget(9), regulator_request_power_budget(9), regulator_free_power_budget(9), regulator_set_mode(9), regulator_get_mode(9), regulator_get_error_flags(9), regulator_set_load(9), regulator_allow_bypass(9), regulator_register_notifier(9), regulator_unregister_notifier(9), regulator_bulk_get(9), regulator_bulk_enable(9), regulator_bulk_disable(9), regulator_bulk_force_disable(9), regulator_bulk_free(9), regulator_handle_critical(9), regulator_notifier_call_chain(9), regulator_mode_to_status(9), regulator_register(9), regulator_unregister(9), regulator_suspend(9), regulator_has_full_constraints(9), rdev_get_drvdata(9), regulator_get_drvdata(9), regulator_set_drvdata(9), rdev_get_id(9)

like, that's the whole friend group, iykyk πŸ’œ


and that's a wrap, bestie!! this cutie lives in ./drivers/regulator and the page is dated October 2026. go forth and register your aliases responsibly πŸ§šβ€β™€οΈπŸŽ€πŸ’–

πŸ“¦ where this page comes from