rio_route_clr_table(9)

💅 rio_route_clr_table(9) — from the Kernel API Manual, bestie 🎀

okay so picture this: you're deep in the Kernel API Manual and you found this lil page called rio_route_clr_table(9) and you're like "what does it even do" — don't worry, I got you 🫶

---

✨ NAME ✨

rio_route_clr_table — literally just clears a switch routing table. that's the whole vibe 💫

---

🌸 SYNOPSIS 🌸

int rio_route_clr_table (struct rio_dev *rdev , u16 table , int lock );

---

🦋 ARGUMENTS 🦋

• rdev — your RIO device, the main character of this whole operation 👑
• table — the routing table ID, like the address on the invite 🎀
• lock — flag for applying a hardware lock on the switch device: 1 = lock, 0 = no_lock 🔒

---

💖 DESCRIPTION 💖

so here's the tea ☕ — if it's available, this calls the switch specific clr_table method to clear a switch routing table. and if that isn't a thing? no stress, it just uses the standard RT write method as defined by the RapidIO specification. slay 💅

and listen, you can pick a specific routing table with the table argument if a switch has per port routing tables — or you can use the standard (aka global) table by passing RIO_GLOBAL_TABLE in table. options, we love to see them 🌈

returns 0 on success, or -EINVAL on failure 😭 (ngl that's the sad path, but at least you know)

---

🧚 SEE ALSO 🧚

okay this list is LONG but we're not skipping a single one, periodt 🔥 — Kernel file ./drivers/rapidio/rio.c:

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_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_request_mport_dma(9), rio_release_dma(9), rio_dma_prep_xfer(9), rio_register_scan(9), rio_mport_scan(9)

bestie that's 48 references and I counted them all by hand, you're welcome 💀💖

---

and that's the whole page!! 🌟 this lil icon lives in ./drivers/rapidio, dated October 2026, and it's signed rio_route_clr_table(9) — muah, go clear some routing tables, ily 🫶💜