quicki2c_acp...dsm_property(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… quicki2c_acpi_get_dsm_property(9) β€” from the Kernel API Manual, bestie πŸŽ€

okay so this one is a kernel API page, and it's literally just one little helper function that goes and asks a device's ACPI DSM parameters what's up. short page, immaculate vibes, let's get into it ✨


🌸 NAME 🌸

quicki2c_acpi_get_dsm_property β€” Query device ACPI DSM parameter πŸ”

✨ SYNOPSIS ✨

int quicki2c_acpi_get_dsm_property (struct acpi_device *adev , const
       guid_t *guid , u64 rev , u64 func , acpi_object_type type , void
       *prop_buf );

πŸ’– ARGUMENTS πŸ’–

  • adev β€” Point to ACPI device 🫢 this is the device you're asking, main character energy fr
  • guid β€” ACPI method's guid πŸŽ€
  • rev β€” ACPI method's revision ⭐
  • func β€” ACPI method's function number πŸ”₯
  • type β€” ACPI parameter's data type 🌈
  • prop_buf β€” Point to return buffer 🧚 this is where the answer lands, no cap

πŸ¦‹ DESCRIPTION πŸ¦‹

So this is a helper function for a device to query its ACPI DSM parameters πŸ’… that's the whole thing, it's giving "small but essential," the way that a single helper function can just make a device's whole day. lowkey iconic.

ngl bestie, the page does not elaborate beyond that β€” no extra behaviour, no secret lore, we simply do not invent facts here πŸ™ˆ

πŸ‘‘ RETURN πŸ‘‘

0 if success or ENODEV on failure πŸ’€

Like, it worked, or the device said "not me, not today" (ENODEV). periodt.

🌟 SEE ALSO 🌟

Kernel file ./drivers/hid/intel-thc-hid/intel-quicki2c/pci-quicki2c.c β€” that's where the actual source lives, go look if you're obsessed πŸ“

and the whole friend group of related functions, all appearing here exactly as listed:


and that's the page!! πŸ’œ it came from the kernel source path <code>./drivers/hid/intel-thc-hid/in...</code> (yeah, it really is truncated like that in the footer, don't come for me πŸ™ˆ) and it's dated October 2026. bye bestie, go query some DSM parameters πŸŽ€βœ¨

πŸ“¦ where this page comes from