__genwqe_wait_ddcb(9)

💖 NAME 💖

__genwqe_wait_ddcb — waits until DDCB is completed. Welcome to the __genwqe_wait_ddcb(9) page from the Kernel API Manual, bestie ✨ This is the function that literally waits for your DDCB to finish, and it’s giving “I’ll hold your spot in the queue” energy 🫶

---

🌸 SYNOPSIS 🌸

int __genwqe_wait_ddcb (struct genwqe_dev *cd , struct ddcb_requ *req );

---

🎀 ARGUMENTS 🎀

• cd — pointer to genwqe device descriptor. That’s your device bestie 💖
• req — pointer to requsted DDCB parameters. The request in question, no cap 🦋

---

🦋 DESCRIPTION 🦋

okay so the Service Layer will update the RETC in DDCB when processing is pending or done. That’s the status-check moment, bestie — RETC gets refreshed while things are pending or when they’re done ✨

When an error is returned, the caller needs to ensure that purge_ddcb is being called to get the req removed from the queue. Do not skip this, fr fr — the req needs its queue exit 💅

---

🔥 RETURN 🔥

• > 0 — remaining jiffies, DDCB completed. Slay, it finished ⭐
• -ETIMEDOUT — when timeout 😭
• -ERESTARTSYS — when ^C 💀
• -EINVAL — when unknown error condition 🙈

---

🌈 SEE ALSO 🌈

the whole friend group is here:

• Kernel file ./drivers/misc/genwqe/card_ddcb.c
• genwqe_crc16(9)
• ddcb_requ_finished(9)
• enqueue_ddcb(9)
• copy_ddcb_results(9)
• genwqe_check_ddcb_queue(9)
• get_next_ddcb(9)
• __genwqe_purge_ddcb(9)
• __genwqe_enqueue_ddcb(9)
• __genwqe_execute_raw_ddcb(9)
• genwqe_next_ddcb_ready(9)
• genwqe_ddcbs_in_flight(9)
• genwqe_card_thread(9)
• genwqe_setup_service_layer(9)
• queue_wake_up_all(9)
• genwqe_finish_queue(9)
• genwqe_release_service_layer(9)

bye bestie 🫶 — source/version corner: ./drivers/misc/genwqe, October 2026, __genwqe_wait_ddcb(9) edition. Catch you on the next man page! 💅