buffer_icap_device_write(9)

💅 buffer_icap_device_write(9)

okay bestie, welcome to the Kernel API Manual ✨ — yes this is a section 9 manpage, we're in kernel-function territory, put your big-girl hat on 🎀

---

🌸 NAME 🌸

buffer_icap_device_write — transfer bytes from ICAP to the storage buffer. that's the whole vibe, that's the whole job 💖

---

✨ SYNOPSIS ✨

int buffer_icap_device_write (struct hwicap_drvdata *drvdata , u32
offset , u32 count );

---

🦋 ARGUMENTS 🦋

• drvdata — a pointer to the drvdata. literally just the driver data pointer, she's the main character we hand everything to 👑
• offset — the storage buffer start address. where in the buffer we're kicking things off 🎯
• count — the number of words (32 bit each, no cap) to read from the device (ICAP). yes bestie, words, not bytes — 32-bit words, keep up 🫶

---

💜 SEE ALSO 💜

• Kernel file ./drivers/char/xilinx_hwicap/buffer_icap.c — go read the source, it's giving lore 📖
• buffer_icap_get_status(9)
• buffer_icap_get_bram(9)
• buffer_icap_busy(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_reset(9)
• buffer_icap_set_configuration(9)
• buffer_icap_get_configuration(9)

the whole friend group fr fr, they all hang out together 🌈

---

ngl, quick vibe check: count is in 32-bit words, not bytes. do not come for me later saying I didn't warn you 😭

---

mwah, that's the page! 💋 this lil masterpiece comes from the source tree at ./drivers/char/xilinx_hwicap, dated October 2026, and it's filed under the name buffer_icap_device_write(9). periodt. 💅✨