ata_qc_issue(9)

💅 ata_qc_issue — issue taskfile to device ✨

okay so you found yourself in the kernel API manual (that's the manual name btw, ata_qc_issue(9) — very demure, very kernel), and you're looking at the function that literally tells an ATA device "go, do the thing." let's get into it 🫶

---

✨ SYNOPSIS ✨

void ata_qc_issue (struct ata_port *ap , struct ata_queued_cmd *qc );

literally two params, no return value, no drama. she just does it. 💅

---

🎀 ARGUMENTS 🎀

• ap — the ATA port of interest 👀 like, which port are we talking about, bestie
• qc — the command we're shipping off to the device 📦 the whole point of the function

---

🌸 DESCRIPTION 🌸

so this is the glow-up phase before submission, okurrr. ata_qc_issue gets an ATA command prepared for submission to the device. and "prepared" is doing a lot of work here, so let me break it down:

• it maps the data into a DMA-able area 🗺️
• it fills in the S/G table 📋
• and finally it writes the taskfile to hardware — which is the moment the command actually starts 🔥 main character moment fr fr

LOCKING: spin_lock_irqsave(host lock) — no cap, that's the lock you hold. don't be weird about it. 💀

---

🦋 SEE ALSO 🦋

these are the neighbors, the acquaintances, the whole extended friend group iykyk. also the kernel file ./drivers/ata/libata-core.c is where the lore lives 📖

ata_link_next(9), ata_dev_next(9), ata_dev_phys_link(9), ata_force_cbl(9), ata_force_pflags(9), ata_force_link_limits(9), ata_force_xfermask(9), ata_force_quirks(9), atapi_cmd_type(9), ata_set_rwcmd_protocol(9), ata_tf_read_block(9), ata_build_rw_tf(9), ata_pack_xfermask(9), ata_unpack_xfermask(9), ata_xfer_mask2mode(9), ata_xfer_mode2mask(9), ata_xfer_mode2shift(9), ata_mode_string(9), ata_dev_classify(9), ata_id_string(9), ata_id_c_string(9), ata_read_native_max_address(9), ata_set_max_sectors(9), ata_hpa_resize(9), ata_dump_id(9), ata_id_xfermask(9), ata_exec_internal(9), ata_pio_need_iordy(9), ata_pio_mask_no_iordy(9), ata_do_dev_read_id(9), ata_dev_read_id(9), ata_dev_power_set_standby(9), ata_dev_power_set_active(9), ata_read_log_page(9), ata_dev_configure(9), ata_cable_40wire(9), ata_cable_80wire(9), ata_cable_unknown(9), ata_cable_ignore(9), ata_cable_sata(9), sata_print_link_status(9), ata_dev_pair(9), ata_timing_cycle2mode(9), ata_down_xfermask_limit(9), ata_set_mode(9), ata_wait_ready(9), ata_wait_after_reset(9), ata_std_prereset(9), ata_std_postreset(9), ata_dev_same_device(9), ata_dev_reread_id(9), ata_dev_revalidate(9), ata_is_40wire(9), cable_is_40wire(9), ata_dev_xfermask(9), ata_dev_set_xfermode(9), ata_dev_set_feature(9), ata_dev_init_params(9), atapi_check_dma(9), ata_std_qc_defer(9), ata_sg_init(9), ata_sg_clean(9), ata_sg_setup(9), swap_buf_le16(9), ata_qc_free(9), ata_qc_complete(9), ata_qc_get_active(9), ata_phys_link_online(9), ata_phys_link_offline(9), ata_link_online(9), ata_link_offline(9), ata_host_suspend(9), ata_host_resume(9), ata_dev_init(9), ata_link_init(9), sata_link_init_spd(9), ata_port_alloc(9), ata_host_alloc(9), ata_host_alloc_pinfo(9), ata_finalize_port_ops(9), ata_host_start(9), ata_host_init(9), ata_host_register(9), ata_host_activate(9), ata_dev_free_resources(9), ata_port_detach(9), ata_host_detach(9), ata_pci_remove_one(9), ata_platform_remove_one(9), ata_msleep(9), ata_wait_register(9)

like. that's the whole group chat. every single one. don't make me @ you again 💜

---

and that's the page bestie!! sig spot at the bottom says this lives in ./drivers/ata and it's dated October 2026, page ata_qc_issue(9) — so if you're reading this in the future, hi, slay, you're doing great 🦋⭐🎀