rio_chk_dev_access(9)

💅 rio_chk_dev_access(9) 💅

okay so bestie, welcome to the Kernel API Manual page for rio_chk_dev_access(9) ✨ the way that this one is short and sweet is sending me 😭 it validates access to the specified device, and that's the whole vibe.

🎀 NAME 🎀

rio_chk_dev_access — validate access to the specified device. periodt 💖

🦋 SYNOPSIS 🦋

here's the exact signature, no cap:

int rio_chk_dev_access (struct rio_dev *rdev );

🌸 ARGUMENTS 🌸

• rdev — pointer to RIO device control structure. that's the argument, bestie, and yes it's a struct rio_dev * 🫶

🌈 SEE ALSO 🌈

Kernel file ./drivers/rapidio/rio.c, plus all these linked besties — every single one, fr fr:

• rio_local_get_device_id(9), rio_query_mport(9), rio_alloc_net(9), rio_local_set_device_id(9), rio_add_device(9)
• rio_request_inb_mbox(9), rio_release_inb_mbox(9), rio_request_outb_mbox(9), rio_release_outb_mbox(9), rio_setup_inb_dbell(9)
• rio_request_inb_dbell(9), rio_release_inb_dbell(9), rio_request_outb_dbell(9), rio_release_outb_dbell(9), rio_add_mport_pw_handler(9)
• rio_del_mport_pw_handler(9), rio_request_inb_pwrite(9), rio_release_inb_pwrite(9), rio_pw_enable(9), rio_map_inb_region(9)
• rio_unmap_inb_region(9), rio_map_outb_region(9), rio_unmap_outb_region(9), rio_mport_get_physefb(9), rio_get_comptag(9)
• rio_set_port_lockout(9), rio_enable_rx_tx_port(9), rio_chk_dev_route(9), rio_mport_chk_dev_access(9), rio_get_input_status(9)
• rio_clr_err_stopped(9), rio_inb_pwrite_handler(9), rio_mport_get_efb(9), rio_mport_get_feature(9), rio_std_route_add_entry(9)
• rio_std_route_get_entry(9), rio_std_route_clr_table(9), rio_lock_device(9), rio_unlock_device(9), rio_route_add_entry(9)
• rio_route_get_entry(9), rio_route_clr_table(9), rio_request_mport_dma(9), rio_release_dma(9), rio_dma_prep_xfer(9)
• rio_register_scan(9), rio_mport_scan(9)

xoxo, your fav kernel bestie 💜 — sign-off from source/version ./drivers/rapidio, dated October 2026, on page rio_chk_dev_access(9) 🎀