rio_device_has_destid(9)

💖 rio_device_has_destid(9) — Kernel API Manual 💖

okay bestie, welcome to the Kernel API Manual page for rio_device_has_destid(9) — yes, that's the whole title, and we're keeping it cute. This one is a little capability check, and it ate. 💅

🌸 NAME 🌸

rio_device_has_destid — Test if a device contains a destination ID register. ✨

✨ SYNOPSIS ✨

the signature, verbatim, no cap:

int rio_device_has_destid (struct rio_mport *port , int src_ops , int
       dst_ops );

🎀 ARGUMENTS 🎀

• port — Master port to issue transaction. 🚀
• src_ops — RIO device source operations. 🌟
• dst_ops — RIO device destination operations. 🎯

💅 DESCRIPTION 💅

okay so it checks the provided src_ops and dst_ops for the necessary transaction capabilities that indicate whether or not a device will implement a destination ID register. that's the whole vibe check. Returns 1 if true or 0 if false. periodt. 💖

🦋 SEE ALSO 🦋

Kernel file ./drivers/rapidio/rio-scan.c — and the whole friend group:

• 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_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_disc_peer(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 bye bestie 🫶 this page comes from ./drivers/rapidio, dated October 2026, and it's literally rio_device_has_destid(9) — slay. 💅