regulator_force_disable(9)
π regulator_force_disable β Kernel API Manual, bestie edition π
okay so you found yourself in the kernel API manual, and specifically you're looking at regulator_force_disable(9). Welcome, this one's a baddie with a very strong opinion. Let's get into it π
β¨ NAME β¨
regulator_force_disable β force disable regulator output. yeah. force. it's giving main character energy and it means it π€
πΈ SYNOPSIS πΈ
int regulator_force_disable (struct regulator *regulator );
π¦ ARGUMENTS π¦
regulatorβ the regulator source. that's your girl. literally the thing you're about to shut off, no questions asked π
π DESCRIPTION π
Forcibly disable the regulator output voltage or current. that's it, that's the whole vibe. no negotiation, no vibes check, no "but what about the other consumers" β it just goes π₯
β οΈ NOTE β οΈ
bestie. listen to me. this will disable the regulator output even if other consumer devices have it enabled. like, even if someone else is still holding it. it does not care. it does not check. it simply disables π«Ά
This should be used for situations when device damage will likely occur if the regulator is not disabled (e.g. over temp). so like β the "we are literally about to cook the hardware" emergency. that's the energy. this is the "break glass in case of overheating" function, not the everyday one π
π RETURN π
0 on success or a negative error number on failure. slay when it's 0, π when it's negative.
π SEE ALSO π
Kernel file ./drivers/regulator/core.c β and honestly the whole group chat of regulator functions:
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_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_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 I said. whole group chat π
and that's the page, bestie β brought to you from ./drivers/regulator, dated October 2026, living under the regulator_force_disable(9) header. mwah, go forth and disable responsibly πβ¨
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms