rio_get_drvdata(9)

💖 rio_get_drvdata — like, the Kernel API Manual page for it ✨

okay so bestie, welcome to rio_get_drvdata(9) — yes that's the manual page name and yes we're gonna get through this together 🫶

---

🌸 NAME 🌸

rio_get_drvdata — the little function that gets you the RIO driver specific data 💅

✨ SYNOPSIS ✨

void * rio_get_drvdata (struct rio_dev *rdev );

look at her. one function, one arg, returns a void *. she's simple, she's iconic, she ate 🔥

🎀 ARGUMENTS 🎀

• rdev — the RIO device in question 🦋 like, the specific one you're asking about. that's it, that's the whole argument.

💜 DESCRIPTION 💜

Okay so the whole vibe here: rio_get_drvdata grabs the RIO driver specific data. That's literally the job.

It returns a pointer to that driver specific data. That pointer is what you get back. void *, as promised. no cap, no extra steps, no side quests 💀

ngl this one is short and sweet — the function does exactly what the NAME says and nothing else. love that for us 🙈

🦋 SEE ALSO 🦋

first up, the kernel file this lives in: ./include/linux/rio_drv.h — go say hi to her 💖

and then, the whole friend group of related calls, all in (9) section glory:

• rio_local_read_config_32(9)
• rio_local_write_config_32(9)
• rio_local_read_config_16(9)
• rio_local_write_config_16(9)
• rio_local_read_config_8(9)
• rio_local_write_config_8(9)
• rio_read_config_32(9)
• rio_write_config_32(9)
• rio_read_config_16(9)
• rio_write_config_16(9)
• rio_read_config_8(9)
• rio_write_config_8(9)
• rio_send_doorbell(9)
• rio_init_mbox_res(9)
• rio_init_dbell_res(9)
• RIO_DEVICE(9)
• rio_add_outb_message(9)
• rio_add_inb_buffer(9)
• rio_get_inb_message(9)
• rio_name(9)
• rio_set_drvdata(9)

and yeah — rio_set_drvdata(9) is literally her other half, the one who sets what she gets. soulmate behavior fr fr 👑 (go read that one too, iykyk)

---

source: ./include/linux · version/date: October 2026 — mwah, that's the whole page bestie, ily, go read your docs 💅✨🎀