mmc_wait_for_req(9)

okay so bestie, welcome to mmc_wait_for_req — the Kernel API Manual, section 9, has entered the chat. This one is literally “start the request, then wait for it to finish” energy, and we’re keeping every detail. 💅

💖 NAME 💖

mmc_wait_for_req — start a request and wait for completion.

✨ SYNOPSIS ✨

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

🎀 ARGUMENTS 🎀

• host — the MMC host to start the command on. 🫶
• mrq — the MMC request to start.

🦋 DESCRIPTION 🦋

So you hand it a host and an mrq, and it starts a new MMC custom command request for that host, then waits for the command to complete. Iconic behavior, no cap. ✨

In the case of 'cap_cmd_during_tfr' requests, the transfer is ongoing, and the caller can issue further commands that do not use the data lines, and then wait by calling mmc_wait_for_req_done. 🧚

It does not attempt to parse the response — like, it is not doing that job, bestie. 💀

🌈 SEE ALSO 🌈

• Kernel file ./drivers/mmc/core/core.c
• mmc_request_done(9)
• mmc_cqe_request_done(9)
• mmc_cqe_post_req(9)
• mmc_is_req_done(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)

mwah 💋 — signing off from ./drivers/mmc/core, October 2026, on the mmc_wait_for_req(9) page 🫶🎀