acpi_check_dsm(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… acpi_check_dsm β€” the kernel API manual, bestie edition

okay so this is acpi_check_dsm from the Kernel API Manual, and honestly? she's a little vibe-checker for _DSM methods. let's get into it πŸŽ€


✨ NAME ✨

acpi_check_dsm β€” literally just checks if the _DSM method supports the functions you're asking about. that's it. that's her whole job 🫢


🌸 SYNOPSIS 🌸

bool acpi_check_dsm (acpi_handle handle , const guid_t *guid , u64 rev ,
       u64 funcs );

she returns a bool btw β€” yes/no energy only πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • handle β€” the ACPI device handle. like, which device are we even talking about, bestie πŸ’…
  • guid β€” the GUID of the requested functions. important: it should be 16 bytes at least, no cap. don't come at her with a short one πŸ™ˆ
  • rev β€” the revision number of the requested functions. which version of the vibe are we on πŸ”₯
  • funcs β€” a bitmap of the requested functions. yes, bitmap. yes, it's giving bit manipulation 🧚

⭐ DESCRIPTION ⭐

so what she does is evaluate the device's _DSM method to check whether it actually supports the functions you're requesting. very "does this spark joy" of her πŸ’–

and a heads up: currently she only supports 64 functions at maximum. which, per the docs, should be enough for now. iconic confidence, honestly πŸ˜­πŸ‘‘


🌈 SEE ALSO 🌈

kernel file ./drivers/acpi/utils.c β€” and all her friends, fr fr:


ngl she's a whole squad. go read them too, iykyk πŸ’œ

okay and finally, the sign-off: this page lives under ./drivers/acpi, dated October 2026, and it's page acpi_check_dsm(9) of the Kernel API Manual. slay, go check your _DSM methods responsibly πŸ“βœ¨

πŸ“¦ where this page comes from