buffer_icap_busy(9)

💅 buffer_icap_busy(9)

okay so bestie, welcome to the Kernel API Manual — this one's a little function with main character energy and it's literally called buffer_icap_busy. yes we're in the (9) section, kernel-functions-only, no cap. let's get into it 🎀

---

✨ NAME ✨

buffer_icap_busy — returns true if the icap device is busy 🫶 that's it, that's the whole vibe check

---

🌸 SYNOPSIS 🌸

bool buffer_icap_busy (void __iomem *base_address );

like, look at her. one arg, one bool, zero drama ✨

---

🦋 ARGUMENTS 🦋

• base_address — the base address of the device. that's the address, bestie, the whole starting point of the device's little memory neighbourhood 💖

---

💜 DESCRIPTION 💜

so what she actually does: this one queries the low order bit of the status register 👀 and that bit is the one that indicates whether the current configuration or readback operation has completed. so yeah — you ask her, she peeks at the low order bit, and you find out what's up. iconic behaviour, honestly.

ngl it's giving "one job, does it well" and we respect that 🌈

---

🎀 SEE ALSO 🎀

kernel file ./drivers/char/xilinx_hwicap/buffer_icap.c — the source, the origin story, the lore 🧚

• buffer_icap_get_status(9)
• buffer_icap_get_bram(9)
• buffer_icap_set_size(9)
• buffer_icap_set_offset(9)
• buffer_icap_set_rnc(9)
• buffer_icap_set_bram(9)
• buffer_icap_device_read(9)
• buffer_icap_device_write(9)
• buffer_icap_reset(9)
• buffer_icap_set_configuration(9)
• buffer_icap_get_configuration(9)

literally the whole friend group, go say hi to all of them 💕

---

ok that's the page!! mwah 💋 this lil family lives in ./drivers/char/xilinx_hwicap and the whole thing is dated October 2026 — so go forth, check your low order bit, and slay 💅✨🍓