rio_disc_peer(9)

💖 rio_disc_peer(9) 💖

okay bestie, this is the Kernel API Manual and we're talking about rio_disc_peer — it's giving recursive RIO network discovery, no cap ✨ Every tiny detail stays, only the vibe got a glow-up 💅

✨ NAME ✨

rio_disc_peer — recursively discovers a RIO network through a master port 🫶

🌸 SYNOPSIS 🌸

int rio_disc_peer (struct rio_net *net , struct rio_mport *port , u16
destid , u8 hopcount , struct rio_dev *prev , int prev_port );

🎀 ARGUMENTS 🎀

okay so here's the cast, and every single one matters:

• net — the RIO network being discovered, periodt 🌈
• port — master port to send transactions 💌
• destid — current destination ID in network 🎯
• hopcount — number of hops into the network 🦋
• prev — previous rio_dev 👀
• prev_port — previous port number 🔢

💫 DESCRIPTION 💫

okay so picture this: rio_disc_peer recursively discovers a RIO network 😭✨ Transactions are sent via the master port passed in port. That's the whole vibe — recursive discovery, master-port transactions, iconic behavior only 💅

🦋 SEE ALSO 🦋

Kernel file lowkey lives at ./drivers/rapidio/rio-scan.c, and the whole SEE ALSO squad is:

• rio_destid_alloc(9)
• rio_destid_reserve(9)
• rio_destid_free(9)
• rio_destid_first(9)
• rio_destid_next(9)
• rio_get_device_id(9)
• rio_set_device_id(9)
• rio_clear_locks(9)
• rio_enum_host(9)
• rio_device_has_destid(9)
• rio_release_dev(9)
• rio_is_switch(9)
• rio_setup_device(9)
• rio_sport_is_active(9)
• rio_get_host_deviceid_lock(9)
• rio_enum_peer(9)
• rio_enum_complete(9)
• rio_mport_is_active(9)
• rio_update_route_tables(9)
• rio_init_em(9)
• rio_enum_mport(9)
• rio_build_route_tables(9)
• rio_disc_mport(9)
• rio_basic_attach(9)

okay bestie, source/version vibe check: ./drivers/rapidio, dated October 2026, and the page is literally rio_disc_peer(9) — slay and goodbye 💖🎀✨