acpi_device...dd_dependent(9)

💖 NAME 💖

acpi_device_power_add_dependent — bestie, this is the one that adds a dependent device to this ACPI device 🫶

---

✨ SYNOPSIS ✨

int acpi_device_power_add_dependent(struct acpi_device *adev, struct device *dev);

---

🎀 ARGUMENTS 🎀

• adev — the ACPI device pointer, the main character of this whole situation 👑
• dev — the dependent device, aka the one tagging along 🌸

---

🦋 DESCRIPTION 🦋

okay so picture this: if adev has a non-empty _PR0, then dev gets added as a dependent device to all the power resources that _PR0 returns. literally all of them 💅

what that means, no cap, is that whenever those power resources get turned _ON, the dependent devices get runtime resumed. iconic behavior honestly ✨

and why do we care? because devices like PCI need this — it lets their driver re-initialize them after the device went to D0uninitialized. yeah. that whole saga 😭

if adev does not have _PR0? this function does absolutely nothing. vibe check: silent, uneventful, no notes 🙈

returns 0 in case of success and a negative errno otherwise. periodt 🔥

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/acpi/power.c
• acpi_device_power_remove_dependent(9)
• acpi_device_sleep_wake(9)
• acpi_turn_off_unused_power_resources(9)

---

💜 that's the whole page, bestie! this one lives in ./drivers/acpi and it's dated October 2026 — go forth and add those dependents, iykyk 🧚‍♀️⭐