of_genpd_ad...ider_onecell(9)
π of_genpd_add_provider_onecell(9) β like, the whole glow-up β¨
okay bestie, welcome to the Kernel API Manual entry for of_genpd_add_provider_onecell. yes the title got truncated in the header, no that's not a vibe killer, we move π
πΈ NAME πΈ
of_genpd_add_provider_onecell β Register a onecell PM domain provider π
β¨ SYNOPSIS β¨
int of_genpd_add_provider_onecell (struct device_node *np , struct
genpd_onecell_data *data );
it's giving "two args, one job, no cap" π₯
π¦ ARGUMENTS π¦
npβ Device node pointer associated with the PM domain provider. like, the actual node bestie, the pointer to it πdataβ Pointer to the data associated with the PM domain provider. the payload, the lore, the whole entire situation π
π§ SEE ALSO π§
the reading list is long girl, buckle up, we're going shopping ποΈ
- Kernel file
./drivers/pmdomain/core.cβ literally the source, go read it, iykyk π
and now the full squad, no one gets left behind, periodt:
dev_pm_genpd_set_performance_state(9)dev_pm_genpd_set_next_wakeup(9)dev_pm_genpd_get_next_hrtimer(9)dev_pm_genpd_set_hwmode(9)dev_pm_genpd_get_hwmode(9)dev_pm_genpd_rpm_always_on(9)dev_pm_genpd_is_on(9)pm_genpd_inc_rejected(9)genpd_queue_power_off_work(9)genpd_power_off(9)genpd_power_on(9)genpd_power_off_work_fn(9)__genpd_runtime_suspend(9)__genpd_runtime_resume(9)genpd_runtime_suspend(9)genpd_runtime_resume(9)genpd_power_off_unused(9)genpd_sync_power_off(9)genpd_sync_power_on(9)genpd_prepare(9)genpd_finish_suspend(9)genpd_suspend_noirq(9)genpd_finish_resume(9)genpd_resume_noirq(9)genpd_freeze_noirq(9)genpd_thaw_noirq(9)genpd_poweroff_noirq(9)genpd_restore_noirq(9)genpd_complete(9)dev_pm_genpd_suspend(9)dev_pm_genpd_resume(9)pm_genpd_add_device(9)pm_genpd_remove_device(9)dev_pm_genpd_add_notifier(9)dev_pm_genpd_remove_notifier(9)pm_genpd_add_subdomain(9)pm_genpd_remove_subdomain(9)pm_genpd_init(9)pm_genpd_remove(9)struct of_genpd_provider(9)genpd_xlate_simple(9)genpd_xlate_onecell(9)genpd_add_provider(9)of_genpd_add_provider_simple(9)of_genpd_del_provider(9)genpd_get_from_provider(9)of_genpd_add_child_ids(9)of_genpd_remove_child_ids(9)of_genpd_add_device(9)of_genpd_add_subdomain(9)of_genpd_remove_subdomain(9)of_genpd_remove_last(9)genpd_dev_pm_detach(9)genpd_dev_pm_attach(9)genpd_dev_pm_attach_by_id(9)genpd_dev_pm_attach_by_name(9)of_genpd_parse_idle_states(9)of_genpd_sync_state(9)
like i said. the whole squad. ate and left no crumbs π
ngl bestie, this page is short and sweet β it's a register-the-provider kinda situation and that's it. no flags, no env vars, no exit statuses, no drama π don't go looking for plot twists that aren't there π
and that's the tea π this one comes from the source ./drivers/pmdomain, dated October 2026, and it's filed under the Kernel API Manual β mwah, go forth and register those PM domains, main character ππ
π¦ 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