rio_register_scan(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌈 rio_register_scan(9) β€” Kernel API Manual 🌈

Okay bestie, welcome to the Kernel API Manual page for rio_register_scan(9). This is the enumeration/discovery method registration interface, and it's giving β€œlet me introduce your fabric scan routine to the right mport” energy. Iconic.

πŸ’– NAME πŸ’–

rio_register_scan β€” the enumeration/discovery method registration interface. No cap, that's the whole name-vibe: you're registering how discovery gets done, and that's main character energy.

✨ SYNOPSIS ✨

int rio_register_scan (int mport_id , struct rio_scan *scan_ops );

πŸŽ€ ARGUMENTS πŸŽ€

  • mport_id β€” the mport device ID for which the fabric scan routine has to be set. Special bestie alert: RIO_MPORT_ANY = set for all available mports.
  • scan_ops β€” the enumeration/discovery operations structure. Literally the ops struct you're handing over.

🌸 DESCRIPTION 🌸

So what does it do? It registers enumeration/discovery operations with the RapidIO subsystem and attaches them to the specified mport device. If you passed RIO_MPORT_ANY, it attaches to all available mports instead. Slay, fr fr.

Vibe check: it returns an error if the mport already has an enumerator attached to it. No double-dipping, bestie β€” that mport is taken.

Plot twist: in the RIO_MPORT_ANY case, it skips mports with valid scan routines, and that skip is not an error. Lowkey polite, highkey convenient. Periodt.

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./drivers/rapidio/rio.c β€” and the whole RapidIO extended universe, iykyk:


Source/version vibe: ./drivers/rapidio; date stamp: October 2026; page title: rio_register_scan(9). Stay fabulous, kernel bestie πŸ’…βœ¨

πŸ“¦ where this page comes from