dev_pm_domai...tach_by_name(9)

🌸 NAME 🌸

dev_pm_domain_attach_by_name — bestie, this one associates a device with one of its PM domains ✨ (this is the dev_pm_domai...tach_by_name(9) page from the Kernel API Manual, iykyk 💅)

🎀 SYNOPSIS 🎀

struct device * dev_pm_domain_attach_by_name (struct device *dev , const char *name );

🦋 ARGUMENTS 🦋

• dev — the device we're using to look up the PM domain 👀 that's the main character here.
• name — the name of the PM domain. literally just the name, no cap 🏷️

💖 DESCRIPTION 💖

Okay so for a detailed function description, you're gonna wanna see dev_pm_domain_attach_by_id. That's where the full lore lives, bestie — this one's not spilling the whole story 🫶

⭐ SEE ALSO ⭐

Kernel file ./drivers/base/power/common.c plus these icons 👑:

• dev_pm_get_subsys_data(9)
• dev_pm_put_subsys_data(9)
• dev_pm_domain_attach(9)
• dev_pm_domain_attach_by_id(9)
• dev_pm_domain_attach_list(9)
• devm_pm_domain_detach_list(9)
• devm_pm_domain_attach_list(9)
• dev_pm_domain_detach(9)
• dev_pm_domain_detach_list(9)
• dev_pm_domain_start(9)
• dev_pm_domain_set(9)
• dev_pm_domain_set_performance_state(9)

okay that's the whole thing, go slay some power management 💅✨ this page lives over in ./drivers/base/power and it's dated October 2026 — periodt, that's the whole sign-off 🌈🎀