acpi_dev_get...consumer_dev(9)

🌸 acpi_dev_get...consumer_dev(9) 🌸

okay bestie so this is a page from the Kernel API Manual and it's literally the whole acpi_dev_get...consumer_dev(9) situation — yes the name has an ellipsis in it, that's just how it is, don't @ me 💅

---

✨ NAME ✨

acpi_dev_get_next_consumer_dev — returns the next adev that's dependent on @supplier 🫶

---

🦋 SYNOPSIS 🦋

struct acpi_device * acpi_dev_get_next_consumer_dev (struct acpi_device
* supplier , struct acpi_device *start );

---

🎀 ARGUMENTS 🎀

• supplier — pointer to the dependee device 👑 (the one everyone's being dependent on, main character energy fr)
• start — pointer to the current dependent device ⭐ (where you're starting from, iykyk)

---

💖 DESCRIPTION 💖

so the way this works is it returns the next struct acpi_device that declares itself dependent on supplier via the _DEP buffer, parsed from the acpi_dep_list. like it's going down the dependency list and handing you the next one, no cap ✨

🚨 important caveat bestie, listen up: if the returned adev is not passed as start to this function, then the caller is responsible for putting the reference to adev when it's no longer needed. so like, you own that reference now, don't just walk away from it 😭💀

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/acpi/scan.c 🍓
• acpi_scan_drop_device(9)
• acpi_fetch_acpi_dev(9)
• acpi_get_acpi_dev(9)
• acpi_dma_supported(9)
• acpi_get_dma_attr(9)
• acpi_dma_get_range(9)
• acpi_dma_configure_id(9)
• acpi_walk_dep_device_list(9)
• acpi_dev_clear_dependencies(9)
• acpi_dev_ready_for_enumeration(9)
• acpi_bus_scan(9)
• acpi_bus_trim(9)

---

and that's the whole page, periodt 💅🦋 this icon lives in ./drivers/acpi and got stamped October 2026 — so like, future vibes only, slay 🌈👑 mwah, go read some kernel source bestie 🎀