of_get_regulator(9)
π of_get_regulator(9) β Kernel API Manual, bestie edition π
Okay so bestie, welcome to the of_get_regulator(9) page β itβs giving βfind me the regulator device node by supply nameβ energy, and honestly? Iconic. Periodt. β¨
β¨ NAME β¨
of_get_regulator β get a regulator device node based on supply name.
πΈ SYNOPSIS πΈ
struct device_node * of_get_regulator (struct device *dev , struct device_node *node , const char *supply );
π ARGUMENTS π
devβ Device pointer fordev_printkmessages. Yep, thatβs the device pointer used for those messages. π«Άnodeβ Device node pointer for supply property lookup. Itβs the node pointer where the supply property gets looked up.supplyβ regulator supply name. Literally the supply name. π
π¦ DESCRIPTION π¦
Extract the regulator device node corresponding to the supply name.
Thatβs the whole vibe: you hand it the supply name, and it extracts the matching regulator device node. No cap. π
π RETURN π
Pointer to the struct device_node corresponding to the regulator if found, or NULL if not found.
So: found = pointer to the struct device_node, not found = NULL. Fr fr. π
π SEE ALSO π
- Kernel file
./drivers/regulator/of_regulator.c of_get_regulator_init_data(9)of_regulator_match(9)of_get_child_regulator(9)of_regulator_dev_lookup(9)of_regulator_get(9)of_regulator_get_optional(9)of_check_coupling_data(9)of_parse_coupled_regulator(9)of_regulator_bulk_get_all(9)
Catch you from ./drivers/regulator, October 2026 β of_get_regulator(9) signing off with main character energy πβ¨π
π¦ 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