ufshcd_mcq_req_to_hwq(9)

💖 ufshcd_mcq_req_to_hwq(9) 💖

okay so bestie, welcome to the Kernel API Manual ✨ this little function is filed under ufshcd_mcq_req_to_hwq(9) and honestly? it's giving "matchmaker but for requests and hardware queues" 🎀

---

🌸 NAME 🌸

ufshcd_mcq_req_to_hwq — literally just: find the hardware queue on which the request would be issued. that's it. that's the whole vibe check 🔥

---

✨ SYNOPSIS ✨

struct ufs_hw_queue * ufshcd_mcq_req_to_hwq (struct ufs_hba *hba ,
struct request *req );

note the spacing in the synopsis — we keep it exactly as-is, no cap 🫶

---

🦋 ARGUMENTS 🦋

• hba — per adapter instance 💜 this is your main character adapter, one per instance, periodt.
• req — pointer to the request to be issued 🌈 hand it over, it's the request you're curious about.

---

⭐ RETURN ⭐

it hands you back the hardware queue instance on which the request will be or has been queued 🎯 (yes, "will be or has been" — it works for both timelines, she's flexible like that 💅).

and if things went sideways: it returns NULL if the request has already been freed 💀 okay so heads up — a NULL back does not mean "no queue found, try again", it means the request is gone. freed. departed. so don't go dereferencing that, bestie, seriously 🙈

---

🎀 SEE ALSO 🎀

kernel file ./drivers/ufs/core/ufs-mcq.c 👑 and the whole squad:

• ufshcd_mcq_config_mac(9)
• ufshcd_mcq_queue_cfg_addr(9)
• ufshcd_get_hba_mac(9)
• ufshcd_mcq_sq_cleanup(9)
• ufshcd_mcq_nullify_sqe(9)
• ufshcd_mcq_sqe_search(9)
• ufshcd_mcq_abort(9)

go read those too, iykyk 🧚

---

fr fr the whole thing lives in ./drivers/ufs/core — that's the source tree neighborhood, and the page is dated October 2026 🌸 so like, we're reading from the future, iconic behavior honestly 💫

and that's the page!! slay, you now understand ufshcd_mcq_req_to_hwq(9) 🍓 bye bestie, go queue something 💖🫶✨