regulator_lock_dependent(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 regulator_lock_dependent(9) 🌸

πŸ’– NAME πŸ’–

Bestie, this is regulator_lock_dependent from the Kernel API Manual β€” the function that locks a regulator's suppliers and coupled regulators. No cap, that's the whole assignment. πŸ’…


✨ SYNOPSIS ✨

void regulator_lock_dependent (struct regulator_dev *rdev , struct ww_acquire_ctx *ww_ctx );

πŸŽ€ ARGUMENTS πŸŽ€

  • rdev β€” regulator source. That's the regulator we're starting from, bestie. 🫢
  • ww_ctx β€” w/w mutex acquire context. Yep, the w/w mutex acquire context β€” it's giving lock-order realness. πŸ”’

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so this function is literally a wrapper on regulator_lock_recursive, and what it does is lock all regulators related with rdev by coupling or supplying. That's it, that's the vibe: related regulators get locked together, and the function is doing the wrapper thing around regulator_lock_recursive. Iconic. πŸ’–βœ¨


🌈 SEE ALSO 🌈

Kernel file ./drivers/regulator/core.c is the home base, and the whole SEE ALSO friend group is: regulator_lock_nested(9), regulator_lock(9), regulator_unlock(9), regulator_lock_two(9), regulator_unlock_two(9), regulator_unlock_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_register_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).


Okay that's the whole page, bestie β€” this cutie is from the ./drivers/regulator source, dated October 2026, and the page title is regulator_lock_dependent(9) in the Kernel API Manual. Bye bestie, go slay those regulator locks! πŸ’…πŸŽ€βœ¨

πŸ“¦ where this page comes from