acpi_resource_consumer(9)

📦 version 7.3.1, in nixpkgs unstable

💅 acpi_resource_consumer(9) — from the Kernel API Manual, bestie

okay so real talk, this is a kernel API manual page and it's genuinely so useful. it's acpi_resource_consumer(9) and it answers the question every nosy little kernel dev asks: who's eating this resource?? 🍓👀 iykyk

✨ NAME ✨

acpi_resource_consumer — find the ACPI device that consumes @res. like, the actual device that's munching on it. we love a good reverse-lookup moment 💅

🌸 SYNOPSIS 🌸

struct acpi_device * acpi_resource_consumer (struct resource *res );

look at her. iconic signature. no notes. 🎀

🦋 ARGUMENTS 🦋

  • res — the resource you're searching for. that's it. that's the whole argument. she's lowkey the main character here 🫶

🔥 DESCRIPTION 🔥

okay so here's the vibe: the function goes through the current resource settings — that's _CRS — of every single ACPI device node, and it looks for res in each one. like a full-on group chat scroll looking for that one message. 📱✨

if it finds an ACPI device whose _CRS includes res, it returns that device. found your culprit, bestie. case closed. 👑

otherwise? it returns NULL. no device is claiming that resource. nothing. crickets. 🦗💀

that's literally it, no cap. simple, clean, does exactly what it says on the tin.

💜 SEE ALSO 💜

the kernel file lives at ./drivers/acpi/resource.c and honestly the whole friend group is worth knowing:

all of them. every single one. we don't skip the squad. 🌈🧚

reminder bestie: this only searches current resource settings (_CRS) on ACPI device nodes. that's the whole scope. don't go expecting it to read your mind or anything 💀

mwah 💋 that's the page! sourced straight from ./drivers/acpi, dated October 2026 — so go forth, find your consumers, and slay ✨👑💖

📦 where this page comes from