buffer_icap_set_rnc(9)

🌸 NAME 🌸

okay so bestie, welcome to the buffer_icap_set_rnc(9) page from the Kernel API Manual ✨ This one is literally here to set the RNC (Readback not Configure) register — that's the whole assignment, and it ate. 💅

✨ SYNOPSIS ✨

the signature, exactly as it slays:

void buffer_icap_set_rnc (void __iomem *base_address , u32 data );

🎀 ARGUMENTS 🎀

• base_address — this contains the base address of the device. like, the device's home base, okay? 🫶
• data — this is the value to be written to the data register. the actual value going in, no cap. 💖

🦋 DESCRIPTION 🦋

okay so the RNC register is lowkey the main character for direction: it determines the direction of the data transfer. It controls whether a configuration or readback take place. 👑

Writing to this register initiates the transfer. yes bestie, the write itself kicks it off — not me explaining a register and getting all excited. 😭

A value of 1 initiates a readback, while writing a value of 0 initiates a configuration. periodt. 💅✨

💜 SEE ALSO 💜

go peek at these if you want the whole friend group:

• Kernel file: ./drivers/char/xilinx_hwicap/buffer_icap.c
• 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_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)

💖 okay bye bestie! this page is from source/version ./drivers/char/xilinx_hwicap, dated October 2026, and it's literally buffer_icap_set_rnc(9) — mwah! 🎀✨