rio_clear_locks(9)
πΈ rio_clear_locks β the kernel API manual, bestie edition πΈ
okay so we're in the <pink>rio_clear_locks(9)</pink> page of the Kernel API Manual, and honestly? this one's a little cleanup queen. let's get into it π
β¨ NAME β¨
rio_clear_locks β releases, like, all the host locks and signals that enumeration is complete π
π¦ SYNOPSIS π¦
int rio_clear_locks (struct rio_net *net );
π ARGUMENTS π
netβ the RIO network we're running on. that's the one. the main character. π
π₯ DESCRIPTION π₯
okay so here's the vibe: it marks the component tag CSR on each device with the enumeration complete flag. yes, every single one, no skipping, we're doing the whole roster π
once that's done β when it's complete β it then releases the host locks on each device. locks: released. hands: washed. no cap. π§Όβ¨
return value check, because we always check:
- returns
0on success π - returns
-EINVALon failure π
π SEE ALSO π
the kernel file lives at ./drivers/rapidio/rio-scan.c β and it's giving extended family, because here's the whole group chat:
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_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_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)
iykyk π«Ά
π friendly reminder that -EINVAL is the failure signal here β if you see that, something went sideways and it's not a vibe.
mwah, that's the page π it's from ./drivers/rapidio, dated October 2026, and it's serving Kernel API Manual energy for rio_clear_locks(9) β slay, go release those locks bestie πβ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms