triflex_bmdma_stop(9)

💅 triflex_bmdma_stop(9) 💅

okay so bestie, welcome to the Kernel API Manual entry for triflex_bmdma_stop(9) — yes that's the whole title, it's giving very "name so long it's basically a scented candle" energy, but we move. 🫶

---

✨ NAME ✨

triflex_bmdma_stop — the DMA stop callback, and honestly? she's the cleanup crew of this whole situation. 🧹

---

🌸 SYNOPSIS 🌸

void triflex_bmdma_stop (struct ata_queued_cmd *qc );

That's it. That's the whole vibe check. A void return, one argument, no drama. 💅

---

🎀 ARGUMENTS 🎀

• qc — an ATA command. literally just "the ATA command", that's the whole description, and we respect the brevity ngl. 👑

---

🦋 DESCRIPTION 🦋

okay so here's the lore. 🌈

We loaded new timings back in dma_start — yes, dma_start, we went there — and as a result of that, we need to restore the PIO timings in dma_stop.

why? because the next command issue needs to get the right clock values. periodt. ⏰

so like... it's a restore-the-timings thing. dma_start changed stuff, dma_stop puts it back so the next command isn't out here running on the wrong clock values. main character energy from dma_stop honestly. 🔥

---

🌟 SEE ALSO 🌟

• Kernel file ./drivers/ata/pata_triflex.c 📁
• triflex_prereset(9)
• triflex_load_timing(9)
• triflex_set_piomode(9)
• triflex_bmdma_start(9) — the one who started it all, iykyk 💀

---

ngl bestie, go read triflex_bmdma_start(9) if you want the before picture — this page is literally the after. 🙈

---

anyway that's the whole page!! mwah 💖 sourced from ./drivers/ata, dated October 2026 — yes, October 2026, she's from the future, we don't ask questions. slay. 🎀🦋✨