ata_acpi_push_id(9)

💖 NAME 💖

okay so bestie, welcome to ata_acpi_push_id(9) from the Kernel API Manual — this one is literally send Identify data to drive, and it's giving kernel side-quest energy. 🦋

ata_acpi_push_id — send Identify data to drive 💅

✨ SYNOPSIS ✨

int ata_acpi_push_id (struct ata_device *dev );

🎀 ARGUMENTS 🎀

• dev — target ATA device, aka the device you're pushing that Identify data toward 👑

🦋 DESCRIPTION 🦋

Okay so here's the lore: this is about the _SDD ACPI object, and it's for SATA mode only. It must be after Identify (Packet) Device — no skipping the order, bestie. It uses its data ATM. The note says this function never returns a failure, and honestly that's the vibe: it's an optional method, so if it fails for whatever reason, we should still just keep going. 🫶

LOCKING: EH context. Keep that in mind, periodt 🔒

🌸 RETURN 🌸

• 0 on success — slay ✨
• -ENOENT if _SDD doesn't exist — it's giving missing icon 😭
• -errno on failure — that's the failure code it gives 💀

🌈 SEE ALSO 🌈

Kernel file: ./drivers/ata/libata-acpi.c

Also go peek at all these besties:

• 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_on_resume(9)
• ata_acpi_set_state(9)
• ata_acpi_on_devcfg(9)
• ata_acpi_on_disable(9)

okay bye bestie 🎀 — this page came from ./drivers/ata, stamped October 2026, and it's all about ata_acpi_push_id(9) 💖