acpi_device_dep(9)
β¨ NAME β¨
okay so bestie, lemme introduce you to acpi_device_dep β the little kernel function (it's acpi_device_dep(9) in the Kernel API Manual, iykyk) that checks ACPI device dependency π
π¦ SYNOPSIS π¦
bool acpi_device_dep (acpi_handle target , acpi_handle match );
π ARGUMENTS π
targetβ the ACPI handle of the target ACPI device. like, the one we're snooping on π΅οΈββοΈmatchβ the ACPI handle we're looking up intarget's_DEPlist. the one we're hunting for π
π₯ DESCRIPTION π₯
Returns true if match is present in the list returned by _DEP for target, or false otherwise. that's it, that's the whole vibe check β does this handle slay in the dependency list or not π
not me being obsessed with how simple that is. periodt π
π SEE ALSO π
Kernel file ./drivers/acpi/utils.c β go read it, fr fr, and then go meet the whole friend group:
acpi_handle_list_equal(9)acpi_handle_list_replace(9)acpi_handle_list_free(9)acpi_evaluate_ost(9)acpi_handle_path(9)acpi_handle_printk(9)__acpi_handle_debug(9)acpi_evaluation_failure_warn(9)acpi_has_method(9)acpi_evaluate_ej0(9)acpi_evaluate_lck(9)acpi_evaluate_reg(9)acpi_evaluate_dsm(9)acpi_check_dsm(9)acpi_dev_uid_to_integer(9)acpi_dev_found(9)acpi_dev_present(9)acpi_dev_get_next_match_dev(9)acpi_dev_get_first_match_dev(9)acpi_reduced_hardware(9)acpi_dev_is_video_device(9)acpi_match_platform_list(9)
π«Ά that's the whole page, bestie β no cap, nothing hidden, every single handle accounted for. go forth and dependency-check π
and that's a wrap on the acpi_device_dep(9) page, brought to you by the fine folks over at ./drivers/acpi, dated October 2026 π she's iconic, she's timeless, she's lowkey just a bool πβ¨πΈ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms