acpi_device_...hysical_node(9)

💅 NAME 💅

acpi_device_is_first_physical_node — bestie, it tells you if this dev is THE first physical node 💖

---

✨ SYNOPSIS ✨

bool acpi_device_is_first_physical_node(struct acpi_device *adev,
                                        const struct device *dev);

---

🎀 ARGUMENTS 🎀

• adev — the ACPI companion device 👑 (yes, the one doing the accompanying)
• dev — the physical device you're side-eyeing and checking 🧐

---

🦋 DESCRIPTION 🦋

Okay so picture this: the function checks whether the dev you handed it is the first physical device attached to the ACPI companion device. Like, is it the main character of this companion situation or not 💅

And why do we even care? Because sometimes the same companion device is shared between, like, many physical devices — the way one group chat has way too many members 🙈 — so this distinction genuinely matters in some cases.

⚠️ Heads up bestie: the caller has to provide a valid adev pointer. No cap. Don't be out here passing garbage, fr fr 😭

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/acpi/bus.c — and the whole friend group:

• acpi_bus_notify(9)
• devm_acpi_install_notify_handler(9)
• acpi_bus_get_primary_device(9)
• acpi_get_first_physical_node(9)
• acpi_of_match_device(9)
• acpi_set_modalias(9)
• acpi_match_acpi_device(9)
• acpi_match_device(9)
• acpi_bus_find_device_by_name(9)
• acpi_early_init(9)
• acpi_subsystem_init(9)

---

That's the whole thing, icon 💜 This little gem lives over in ./drivers/acpi, its version stamp is October 2026, and it's serving acpi_device_...hysical_node(9) realness. Slay, go check your physical nodes 🫶✨