iio_get_acp...ame_and_data(9)
π iio_get_acpi_device_name_and_data(9) π
okay so bestie, welcome to the Kernel API Manual β yes we're doing kernel API today and honestly? it's giving main character energy β¨ this one lives in the IIO subsystem and it's a little lookup helper, so let's get into it π«Ά
β¨ NAME β¨
iio_get_acpi_device_name_and_data β literally just returns the ACPI device instance name and the driver data. that's the whole vibe, no cap π
πΈ SYNOPSIS πΈ
const char * iio_get_acpi_device_name_and_data (struct device *dev ,
const void **data );
π¦ ARGUMENTS π¦
devβ the Device structure, iykyk πdataβ an optional pointer that hands you back the driver data β
π DESCRIPTION π
so picture this: your device got enumerated by ACPI ID matching (yes, that's a thing, slay) and now the user lowkey wants to set a description for the physical chip π in cases like that, the ACPI device instance name might be the move. this call exists so you can go retrieve that info β it's literally the whole point of the function π
π NOTE π
β οΈ bestie listen to me: this helper function exists only for backward compatibility. do not use it in new code, fr fr π it's a legacy icon, not a blueprint π
π₯ RETURN π₯
the ACPI device instance name β or NULL. that's it, that's the return π
π§ SEE ALSO π§
- Kernel file
./drivers/iio/industrialio-acpi.cπ iio_read_acpi_mount_matrix(9)β¨
okay that's the whole page, you ate that π«Ά and for the credits bestie: this cutie comes from ./drivers/iio, dated October 2026 β periodt πππ¦
π¦ 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