ata_acpi_on_devcfg(9)
πΈ ata_acpi_on_devcfg(9) πΈ
okay so this is a page from the Kernel API Manual, bestie β yes, the Kernel API Manual, we're in the big leagues now π
β¨ NAME β¨
ata_acpi_on_devcfg β the ATA ACPI hook that gets called on device donfiguration π
not me pointing out that the original literally says "donfiguration" β that's their typo, not mine, I'm just being faithful to the source π
β¨ SYNOPSIS β¨
int ata_acpi_on_devcfg (struct ata_device *dev );
β¨ ARGUMENTS β¨
devβ the target ATA device π¦ like, the actual device we're doing all this for
β¨ DESCRIPTION β¨
so here's the vibe: this function gets called when dev is about to be configured. main character moment incoming π₯
and listen β the IDENTIFY data might have been modified after this hook is run. so don't go assuming it's frozen in time, okay? things change, data changes, we love growth π
LOCKING: EH context. that's the rule, no cap π«Ά
β¨ RETURN β¨
- a positive number β meaning yes babes, the IDENTIFY data needs to be refreshed π
0β nope, it's fine, we're good β¨-errnoβ something went wrong π on failure, as usual
β¨ SEE ALSO β¨
the kernel file lives at ./drivers/ata/libata-acpi.c β that's the home base π
and it comes with a whole friend group, fr fr:
ata_dev_acpi_handle(9)ata_acpi_handle_hotplug(9)ata_acpi_dev_manage_restart(9)ata_acpi_port_power_on(9)ata_acpi_dissociate(9)ata_acpi_gtm(9)ata_acpi_stm(9)ata_dev_get_GTF(9)ata_acpi_gtm_xfermask(9)ata_acpi_cbl_pata_type(9)ata_acpi_run_tf(9)ata_acpi_exec_tfs(9)ata_acpi_push_id(9)ata_acpi_on_resume(9)ata_acpi_set_state(9)ata_acpi_on_disable(9)
aaaand that's the whole page, bestie π§ sign-off time: this one comes from ./drivers/ata, dated October 2026, and it's filed under ata_acpi_on_devcfg(9). slay π
π
π¦ 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