pci_doe_submit_task(9)

💅 pci_doe_submit_task — kernel API manual, bestie edition 🎀

Okay so this one lives in the Kernel API Manual, and honestly? It's giving "small function, big responsibilities." Let's get into it ✨

---

🌸 NAME 🌸

pci_doe_submit_task — submit a task to be processed by the state machine 🧚

---

🦋 SYNOPSIS 🦋

int pci_doe_submit_task (struct pci_doe_mb *doe_mb , struct pci_doe_task
*task );

---

💜 ARGUMENTS 💜

• doe_mb — the DOE mailbox capability you're submitting to. Like, the destination, the vibe, the whole point 📬
• task — the task you're queuing up. This is the thing that's gonna go do the thing.

---

✨ DESCRIPTION ✨

So what this does is: you submit a DOE task (request/response, the whole combo) to the DOE mailbox, and it gets processed. The function returns as soon as the task object is queued up — it's not waiting around for the whole thing to finish, no cap. 💅

But — and this is the important bit — if the queue is full, this function will sleep until there's room in the queue. Not "return an error," not "spin," it straight up naps 😴 So like, don't call it somewhere where sleeping is illegal, iykyk.

task->complete will be called when the state machine is done processing this task. That's your callback, your moment, your main character energy 👑

⚠️ task must be allocated on the stack. Fr fr, this is not optional. Heap-allocated tasks? Not the move, bestie. 🫶

Also: excess data will be discarded. If you're sending more than fits, the extra just gets dropped. Gone. Not invited to the party 💀

---

🔥 RETURN 🔥

• 0 — when the task has been successfully queued 🎉
• -ERRNO — on error 😭

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/pci/doe.c
• struct pci_doe_mb(9)
• struct pci_doe_task(9)
• pci_doe_create_mb(9)
• pci_doe_destroy_mb(9)
• pci_doe_supports_feat(9)
• pci_doe(9)
• pci_find_doe_mailbox(9)

---

And that's the whole page, bestie 🍓 It ships out of ./drivers/pci, dated October 2026, and it's the pci_doe_submit_task(9) page — go queue something iconic 💖✨