rio_match_device(9)
rio_match_device(9) πΈ
welcome to the Kernel API Manual, bestie β this one is all about rio_match_device(9) and it's lowkey iconic π
β¨ NAME β¨
rio_match_device β tell if a RIO device has a matching RIO device id structure. That's the whole vibe π«Ά
πΈ SYNOPSIS πΈ
okay so here's the exact signature, no cap:
const struct rio_device_id * rio_match_device (const struct
rio_device_id *id , const struct rio_dev *rdev );
it returns a const struct rio_device_id *, and it takes id and rdev. periodt β¨
π ARGUMENTS π
idβ the RIO device id structure to match against π―rdevβ the RIO device structure to match against π―
π¦ DESCRIPTION π¦
okay so bestie, this function is used from driver probe and bus matching to check whether a RIO device matches a device id structure provided by a RIO driver. it's giving "do these two belong together?" energy π
it returns the matching struct rio_device_id or NULL if there is no match. so yeah β match found? you get the matching struct rio_device_id. no match? NULL, and that's that. no cap π
π₯ SEE ALSO π₯
Kernel file ./drivers/rapidio/rio-driver.c is right here, and the whole squad is:
rio_dev_get(9)rio_dev_put(9)rio_device_probe(9)rio_device_remove(9)rio_register_driver(9)rio_unregister_driver(9)rio_match_bus(9)rio_bus_init(9)
cute sign-off: source/version ./drivers/rapidio, date October 2026 β bye bestie, go match those devices ππ¦
π¦ 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