mmc_is_req_done(9)

💖 NAME 💖

Okay bestie, welcome to the mmc_is_req_done(9) page from the Kernel API Manual ✨ This one is literally about determining if a 'cap_cmd_during_tfr' request is done. That’s the whole vibe 🎀

✨ SYNOPSIS ✨

bool mmc_is_req_done (struct mmc_host *host , struct mmc_request *mrq );

No cap, that’s the function signature, copied exactly so you don’t have to squint 💅

🫶 ARGUMENTS 🫶

• host — MMC host. The main character of the hardware side 🎀
• mrq — MMC request. The request bestie getting checked 🌸

🌟 DESCRIPTION 🌟

Okay so here’s the tea: mmc_is_req_done is used with requests that have mrq->cap_cmd_during_tfr = true. Highkey important, bestie 🦋

mmc_is_req_done must be called after starting a request and before waiting for it to complete. That is, either in between calls to mmc_start_req, or after mmc_wait_for_req and before mmc_wait_for_req_done. Fr fr, those are the timing windows 👑

If it is called at other times the result is not meaningful. Like, not “oops tiny typo” not meaningful — the result just isn’t meaningful, periodt 😭

🌈 SEE ALSO 🌈

Kernel file ./drivers/mmc/core/core.c — the kernel file reference for this whole situation 📚

• mmc_request_done(9)
• mmc_cqe_request_done(9)
• mmc_cqe_post_req(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)

That’s the whole page, bestie 💜 This beauty lives under ./drivers/mmc/core and is dated October 2026 — mmc_is_req_done(9) signing off 🫶✨