rio_write_config_32(9)
okay bestie, welcome to the rio_write_config_32(9) page from the Kernel API Manual β yes, we're doing kernel config-space business and we're gonna make it cute β¨
β¨ NAME β¨
rio_write_config_32 - Write 32 bits to configuration space π
πΈ SYNOPSIS πΈ
int rio_write_config_32 (struct rio_dev *rdev , u32 offset , u32 data );
π ARGUMENTS π
rdevβ the RIO device, aka the main character here π«Άoffsetβ the offset into the device configuration space; think of it as the exact little spot you're aiming at π―dataβ the data to be written, no cap πΎ
π¦ DESCRIPTION π¦
okay so this function writes 32 bits of data to the specified offset within the RIO device's configuration space. that's the vibe: 32 bits, one offset, one RIO device's config space, slay β¨
β SEE ALSO β
Kernel file: ./include/linux/rio_drv.h β yes bestie, that's where the header lives π
the whole squad:
rio_local_read_config_32(9)rio_local_write_config_32(9)rio_local_read_config_16(9)rio_local_write_config_16(9)rio_local_read_config_8(9)rio_local_write_config_8(9)rio_read_config_32(9)rio_read_config_16(9)rio_write_config_16(9)rio_read_config_8(9)rio_write_config_8(9)rio_send_doorbell(9)rio_init_mbox_res(9)rio_init_dbell_res(9)RIO_DEVICE(9)rio_add_outb_message(9)rio_add_inb_buffer(9)rio_get_inb_message(9)rio_name(9)rio_get_drvdata(9)rio_set_drvdata(9)
mwah π this cutie comes from ./include/linux, dated October 2026, and rio_write_config_32(9) is literally signing off β periodt π«Άπ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms