acpi_get_fir...hysical_node(9)

✨ acpi_get_fir...hysical_node(9) ✨

okay so bestie, welcome to the Kernel API Manual 🎀 — this one lives in section 9 and honestly it's giving "small function, big main character energy". Let's get into it 💅

---

🌸 NAME 🌸

acpi_get_first_physical_node — literally just finds the first physical node of an ACPI device. that's it. that's the whole vibe 🦋

---

⭐ SYNOPSIS ⭐

struct device * acpi_get_first_physical_node (struct acpi_device *adev );

like, you hand it an ACPI device and it hands you back a struct device *. simple as 🫶

---

💖 ARGUMENTS 💖

• adev — the ACPI device in question 👀 (yes, that one. the one you're asking about.)

---

🔥 RETURN 🔥

the first physical node of the ACPI device adev ✨ that's the whole return value, no cap.

---

🦋 SEE ALSO 🦋

kernel file ./drivers/acpi/bus.c — go read it, iykyk 📖

and the whole friend group of related functions, all here, none skipped, periodt:

• acpi_bus_notify(9)
• devm_acpi_install_notify_handler(9)
• acpi_bus_get_primary_device(9)
• acpi_device_is_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)

---

and that's the whole page, bestie 💜 this one came out of ./drivers/acpi, dated October 2026, and it's filed under acpi_get_fir...hysical_node(9) — yes the title is truncated with ellipsis in the header, that's just how it is, don't come for me 😭 slay, go forth and find those physical nodes 👑