acpi_dev_uid_match(9)

💅 acpi_dev_uid_match(9) — like, the Kernel API Manual, bestie 🎀

okay so picture this: you're deep in the kernel, you've got an ACPI device in one hand and a UID in the other, and you just need to know if they're a match. that's literally it. that's the whole function. no cap. this page lives in the Kernel API Manual and it's short and sweet and honestly kind of iconic for it.

---

✨ NAME ✨

acpi_dev_uid_match — match device by supplied UID 🦋

like, you give it a device, you give it a UID, and it tells you if they vibe together. periodt.

---

🌸 SYNOPSIS 🌸

acpi_dev_uid_match (adev , uid2 );

that's the whole call. two things in, one truth value out. ate and left no crumbs 🔥

---

🎀 ARGUMENTS 🎀

• adev — the ACPI device you're trying to match. this is your main character ✨
• uid2 — the Unique ID of the device, aka the thing you're checking it against. the vibe check in question 💅

---

💖 DESCRIPTION 💖

so what does it actually do? it matches the UID in adev against the given uid2. that's the tea. one device, one UID, one comparison. lowkey obsessed with how straightforward this is 🫶

---

👑 RETURN 👑

• true if it matches 🌈
• false otherwise 💀

that's it. binary. no in-between. no "maybe". it's giving decisive.

---

🧚 SEE ALSO 🧚

siblings in the acpi_bus family, iykyk:

• Kernel file ./include/acpi/acpi_bus.h struct
• acpi_device_software_node_port(9)
• acpi_device_software_nodes(9)
• acpi_dev_hid_uid_match(9)
• for_each_acpi_consumer_dev(9)
• for_each_acpi_dev_match(9)

go read those too, bestie, they're all right there in the same header 💜

---

ngl this one's a quick read — but don't let the short page fool you, every single detail above is load-bearing 🍓

k bye, this page ships out of ./include/acpi in October 2026, version vibes courtesy of the Kernel API Manual — mwah 💋 ⭐