STRUCT RIO_DEV(9)

💜 struct rio_dev(9) 💜

okay so bestie, welcome to the struct rio_dev glow-up page, straight outta the Kernel API Manual. this is the iconic little struct that holds all the RIO device info, and we're gonna walk through every single field together because you deserve to know 😤✨

---

🎀 NAME 🎀

struct rio_dev — RIO device info. that's it, that's the vibe. it's the blueprint, the main character, the whole personality 💅

---

✨ SYNOPSIS ✨

here's the whole gorgeous thing, no cap, copied exactly:

struct rio_dev {
    struct list_head global_list;
    struct list_head net_list;
    struct rio_net *net;
    bool do_enum;
    u16 did;
    u16 vid;
    u32 device_rev;
    u16 asm_did;
    u16 asm_vid;
    u16 asm_rev;
    u16 efptr;
    u32 pef;
    u32 swpinfo;
    u32 src_ops;
    u32 dst_ops;
    u32 comp_tag;
    u32 phys_efptr;
    u32 phys_rmap;
    u32 em_efptr;
    u64 dma_mask;
    struct rio_driver *driver;
    struct device dev;
    struct resource riores[RIO_MAX_DEV_RESOURCES];
    int (*pwcback) (struct rio_dev *rdev, union rio_pw_msg *msg, int
step);
    u16 destid;
    u8 hopcount;
    struct rio_dev *prev;
    atomic_t state;
    struct rio_switch rswitch[];
 };

the way that function pointer wraps onto its own line? she's doing her best, we love her 🫶

---

🌸 Members 🌸

okay bestie, grab a snack, we're going through all of them 🍓

• global_list — the node in the list of all RIO devices. every device's in this group chat 💬
• net_list — node in the list of RIO devices in a network. smaller, cozier group chat 🦋
• net — the network this device is a part of. found family 🥹
• do_enum — the enumeration flag. yes/no bestie, are we enumerating ✨
• did — Device ID 🔥
• vid — Vendor ID 💖
• device_rev — Device revision, glow-up history 📈
• asm_did — Assembly device ID 🧚
• asm_vid — Assembly vendor ID 🎀
• asm_rev — Assembly revision ⭐
• efptr — Extended feature pointer 👑
• pef — Processing element features 💅
• swpinfo — Switch port info 🌈
• src_ops — Source operation capabilities 💜
• dst_ops — Destination operation capabilities 💜
• comp_tag — RIO component tag 🏷️
• phys_efptr — RIO device extended features pointer 🔍
• phys_rmap — LP-Serial Register Map Type (literally 1 or 2, those are the options, no others, periodt) 🫶
• em_efptr — RIO Error Management features pointer 😭
• dma_mask — Mask of bits of RIO address this device implements. important, do not skip 💀
• driver — the driver that's claiming this device. it's taken bestie 🙈
• dev — the device model device 🎀
• riores — the RIO resources this device owns. hers. don't touch 🌸
• pwcback — the port-write callback function for this device. it's typed as int (*pwcback) (struct rio_dev *rdev, union rio_pw_msg *msg, int step) for the record ✨
• destid — Network destination ID (or, for a switch, the associated destid) 📍
• hopcount — the hopcount to this device. how many hops, exactly, that's the whole job 🦋
• prev — the previous RIO device connected to the current one. linked list lore 🔗
• state — device state, keeping track of where we're at 🫶
• rswitch — a struct rio_switch, if it's valid for this device 👑

ok quick heads up bestie: rswitch is a flexible array member (see those [] brackets?), so it's only there when it's valid for the device. do not go poking past it, that's giving undefined behaviour energy 💀

---

🦋 SEE ALSO 🦋

kernel file ./include/linux/rio.h has the whole family album, plus these icons:

struct rio_switch(9), struct rio_switch_ops(9), struct rio_msg(9), struct rio_dbell(9), struct rio_mport(9), struct rio_net(9), struct rio_mport_attr(9), struct rio_ops(9), struct rio_driver(9), struct rio_scan(9), struct rio_scan_node(9)

go read them all, i'll wait 🧚✨

---

and that's the whole page bestie!! it lives over in ./include/linux and it was dated October 2026 — so like, keep that in mind if anything looks different later, mwah 💋🎀💜