mmc_cqe_request_done(9)

💅 mmc_cqe_request_done — like, the Kernel API Manual, bestie ✨

okay so real talk, you're in the mmc_cqe_request_done(9) page of the Kernel API Manual and it's honestly giving "small function, big responsibilities" energy. let's get into it 🎀

---

✨ NAME ✨

mmc_cqe_request_done — CQE has finished processing an MMC request 🦋

like, that's the whole vibe. CQE is done, the request is done, we're wrapping it up. periodt.

---

🌸 SYNOPSIS 🌸

void mmc_cqe_request_done (struct mmc_host *host , struct mmc_request
*mrq );

yes bestie it's a void function, meaning it returns literally nothing — it just does the thing and dips 💅

---

🫶 ARGUMENTS 🫶

• host — the MMC host which completed the request. this is the main character of the operation, no cap 👑
• mrq — the MMC request which completed. the request in question. the one that's, like, done done ✨

---

🧚 DESCRIPTION 🧚

okay so listen up: CQE drivers should call this function when they have completed their processing of a request.

that's it. that's the assignment. you finished processing the request, you call mmc_cqe_request_done, everybody's happy, the kernel is slaying, we move on 🎀 it's giving "closing the loop" and honestly we're obsessed 🌈

fr fr, the key word here is when they have completed their processing — don't be out here calling it early, bestie, that's not the vibe 😭

---

🔥 SEE ALSO 🔥

the kernel file ./drivers/mmc/core/core.c lives here, and it's also friends with all of these icons:

• mmc_request_done(9)
• mmc_cqe_post_req(9)
• mmc_is_req_done(9)
• mmc_wait_for_req(9)
• mmc_wait_for_cmd(9)
• mmc_set_data_timeout(9)
• __mmc_claim_host(9)
• mmc_release_host(9)
• mmc_vdd_to_ocrbitnum(9)
• mmc_vddrange_to_ocrmask(9)
• mmc_handle_undervoltage(9)
• mmc_detect_change(9)
• mmc_erase(9)
• mmc_hw_reset(9)

---

and that's the whole page, bestie 🫶 before you go — this one's from ./drivers/mmc/core, dated October 2026, so like… mark your calendars 💖 mwah, go finish those requests ✨🎀