acpi_bus_scan(9)

🦋 NAME 🦋

Hiii bestie, welcome to the Kernel API Manual entry for acpi_bus_scan(9) — it literally adds ACPI device node objects in a given namespace scope. 💅✨

🌸 SYNOPSIS 🌸

int acpi_bus_scan (acpi_handle handle );

🎀 ARGUMENTS 🎀

• handle — Root of the namespace scope to scan. 🫶

💖 DESCRIPTION 💖

So basically: scan a given ACPI tree (probably recently hot-plugged, iykyk) and create and add the devices it finds. 🌈

If no devices were found, -ENODEV is returned — but bestie, that does not mean there’s been a real error. 😭 There just have been no suitable ACPI objects in the table trunk from which the kernel could create a device and add an appropriate driver. It’s giving “empty group chat,” not “emergency.” 💀

Important caveat: this must be called under acpi_scan_lock. No cap. 🔥

🌟 SEE ALSO 🌟

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

• 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_dev_get_next_consumer_dev(9)
• acpi_bus_trim(9)

Okay bye bestie 💋 this page is from ./drivers/acpi, dated October 2026, and it’s literally acpi_bus_scan(9) — mwah 🫶🎀