_regulator_...atus_enabled(9)
β¨ _regulator_check_status_enabled β the vibe check for your regulator β¨
okay so bestie, you're reading a page from the Kernel API Manual and honestly? it's a short one, we love a low-effort icon π this little function's whole job is to look at a regulator's status and be like "does this count as enabled or not" β that's it, that's the plot π
the actual brains live over in the kernel file ./drivers/regulator/core.c, so go say hi if you want the lore π¦
πΈ NAME πΈ
_regulator_check_status_enabled β check if regulator status can be interpreted as "regulator is enabled" π
like, it doesn't change anything, it just β¨interpretsβ¨. no cap, it's giving "let me read the room" energy π§
π SYNOPSIS π
int _regulator_check_status_enabled (struct regulator_dev *rdev );
π¦ ARGUMENTS π¦
rdevβ the regulator device to check π«Ά that's the main character of this whole page, the regulator device you're side-eyeing to find out what's going on with it β¨
π RETURN π
so here's what you might get back, and every single one matters, so pay attention bestie:
1β if status shows regulator is in enabled state π slay, it's on, we're so back0β if it's not enabled state π okay so it's not on, noted- Error Value β as received from
ops->get_statusπ like, whatever error came back fromops->get_statusgets handed straight to you, no editing, no filtering, no "let me clean that up for you" energy π
ngl, that third one is important β the function isn't out here inventing new errors or translating anything. it passes along what ops->get_status gave it, fr fr π«Ά
π SEE ALSO π
okay this list is iconic in length, like the function is small but the friend group is HUGE π every single one of these, bestie, no skipping:
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_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)
and that's the whole page, bestie π«Ά short, sweet, and it lives its life in the kernel file ./drivers/regulator/core.c π mwah π
this lil cutie comes to you courtesy of ./drivers/regulator, dated October 2026 β periodt π
π¦ 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