fifo_icap_r...fo_occupancy(9)

🦋 NAME 🦋

ok bestie, so fifo_icap_read_fifo_occupancy — literally what it says on the tin: Query the read fifo available data. that's the whole vibe 💅

and yeah, this is living in the Kernel API Manual, section 9, so you already know it's some kernel-space main character energy ✨

---

🎀 SYNOPSIS 🎀

u32 fifo_icap_read_fifo_occupancy (struct hwicap_drvdata *drvdata );

that's it. one function, one arg, returns a u32. no cap, it's giving "small but mighty" 🫶

---

🌸 ARGUMENTS 🌸

• drvdata — a pointer to the drvdata. that's literally the description, ok, i'm not gonna invent lore 😭 just hand it the drvdata pointer and let it cook.

---

⭐ RETURN ⭐

it gives you back the number of words that can be safely read from the read fifo. 🔥 "safely" is doing a lot of heavy lifting there, so don't go reading more than that, bestie — respect the number 🫡

---

🌈 SEE ALSO 🌈

ok so the whole friend group, in order, no one left out 🫶

• Kernel file ./drivers/char/xilinx_hwicap/fifo_icap.c
• 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_write_fifo_vacancy(9)
• fifo_icap_set_configuration(9)
• fifo_icap_get_configuration(9)
• fifo_icap_reset(9)
• fifo_icap_flush_fifo(9)

---

💖 that's the whole page, i fear. go read your fifo occupancy and slay ✨

and that's a wrap, bestie — big kisses from ./drivers/char/xilinx_hwicap, dated October 2026 🎀🦋 see u never, mwah 💜