efi_capsule_pending(9)

✨ efi_capsule_pending 💅

okay so bestie, welcome to the Kernel API Manual — yes we're reading kernel docs together, this is our bonding time 🫶

---

🌸 NAME 🌸

efi_capsule_pending — has a capsule been passed to the firmware? 👀 like, is it pending or not, that's the whole vibe check

---

🎀 SYNOPSIS 🎀

bool efi_capsule_pending (int *reset_type );

---

💖 ARGUMENTS 💖

• reset_type — this is where you stash the type of EFI reset if a capsule is pending. it's literally the output slot, bestie, that's its whole job 🫡

---

🦋 DESCRIPTION 🦋

so here's the tea ☕ — to make sure the registered capsule gets processed correctly by the firmware, we have to perform a specific type of reset. so: if a capsule is pending, this function returns the reset type in reset_type. that's it, that's the deal ✨

⚠️ race condition alert, no cap — this function will race with callers of efi_capsule_update. like, for example: you call this function while somebody else is in efi_capsule_update but hasn't reached efi_capsue_update_locked yet — you will miss the updates to capsule_pending and efi_reset_type after efi_capsule_update_locked completes. 😭 rip

a non-racy use is from platform reboot code, because we use system_state to make sure no capsules can be sent to the firmware once we're at SYSTEM_RESTART. iconic behavior honestly 👑 see efi_capsule_update_locked.

---

🔥 SEE ALSO 🔥

kernel file ./drivers/firmware/efi/capsule.c — and also go read:

• efi_capsule_supported(9)
• efi_capsule_update_locked(9)
• efi_capsule_update(9)

---

okay that's the whole page, go forth and know thy capsules 🧚💜

— source/version: ./drivers/firmware/efi — dated October 2026 ✨ slay, see you in the next manpage bestie 🎀