stm32_hash_wait_busy(9)

💖 stm32_hash_wait_busy(9) 💖

okay bestie, so this one lives in the Kernel API Manual and honestly? it's a whole mood. it's the function that just waits — patiently, main-character-style — until the hash processor is free to do its thing. and if the hash core is out here taking more than 10 ms to chew through a block of data, this baby doesn't just vibe silently, it returns an error. periodt. 👑

---

✨ NAME ✨

stm32_hash_wait_busy — wait until hash processor is available. It return an error if the hash core is processing a block of data for more than 10 ms.

(not me keeping that exact wording, iykyk — the facts stay, only the fit changes 💅)

---

🌸 SYNOPSIS 🌸

int stm32_hash_wait_busy (struct stm32_hash_dev *hdev );

like, one function, one argument, zero drama. 🦋

---

🎀 ARGUMENTS 🎀

• hdev — the stm32_hash_dev device. that's the whole thing, bestie — your little handle to the hardware, and the function wants it so it knows which hash processor to stare at while it waits 💜

---

🔥 SEE ALSO 🔥

• Kernel file ./drivers/crypto/stm32/stm32-hash.c — the whole lore lives here, go read it, it's giving source of truth ✨
• stm32_hash_set_nblw(9) — the friend in the group chat 🫶
• stm32_hash_write_ctrl(9) — the other friend in the group chat 🫶

---

ngl, the hard limit is real: past 10 ms of processing a block of data and you're getting an error back, not a happy ending. 😭 so yeah, this is not an infinite wait — highkey keep that in mind.

---

okay that's the whole page, no cap 🌈 — this absolute icon of a manual page came to you from ./drivers/crypto/stm32, dated October 2026, and honestly? a slay. 🎀💖✨