fifo_icap_wr...fifo_vacancy(9)

✨ NAME ✨

okay so bestie, welcome to the fifo_icap_wr...fifo_vacancy(9) page — this one is all about fifo_icap_write_fifo_vacancy, and its whole vibe is query the write fifo available space 💅✨

🌸 SYNOPSIS 🌸

u32 fifo_icap_write_fifo_vacancy (struct hwicap_drvdata *drvdata );

that's the exact signature, no cap — copy it character for character 🫶

🎀 ARGUMENTS 🎀

• drvdata — a pointer to the drvdata. that's literally it, that's the argument 💖

🦋 RETURN 🦋

it gives you back the number of words that can be safely pushed into the write fifo 🔥 — yes, u32 energy, and the count is the whole point ✨

👑 SEE ALSO 👑

go peek at the kernel file ./drivers/char/xilinx_hwicap/fifo_icap.c and these iconic neighbors:

• fifo_icap_fifo_write(9)
• fifo_icap_fifo_read(9)
• fifo_icap_set_read_size(9)
• fifo_icap_start_config(9)
• fifo_icap_start_readback(9)
• fifo_icap_get_status(9)
• fifo_icap_busy(9)
• fifo_icap_read_fifo_occupancy(9)
• fifo_icap_set_configuration(9)
• fifo_icap_get_configuration(9)
• fifo_icap_reset(9)
• fifo_icap_flush_fifo(9)

k bye bestie, this page comes from ./drivers/char/xilinx_hwicap, dated October 2026, and its manual name is fifo_icap_wr...fifo_vacancy(9) 🫶✨💜