RIO_LOP_READ(9)

💅 RIO_LOP_READ(9) — bestie's guide to the Kernel API Manual

okay so sit down, grab a strawberry 🍓, because we're talking about RIO_LOP_READ and honestly? it's giving macro-that-does-your-homework-for-you energy. this is a page straight outta the Kernel API Manual and it's lowkey iconic 💖

✨ NAME ✨

RIO_LOP_READ — the macro that generates all your rio_local_read_config_* functions ✨ like it literally births them, no cap. it's giving factory vibes 🏭💅

🎀 SYNOPSIS 🎀

RIO_LOP_READ (size , type , len );

that's it. three little args. so simple it hurts 😭🫶

🦋 ARGUMENTS 🦋

• size — the size of the configuration space read, in bits — and bestie, it's 8, 16, or 32 bits only, iykyk, don't get creative 🙈
• type — the C type of the value argument. like, what kind of little guy are we storing this in 🔥
• len — the length of the configuration space read, measured in bytes — that's 1, 2, or 4 bytes, periodt 💀

ngl, the pairing is real: 8 bits ↔ 1 byte, 16 ↔ 2, 32 ↔ 4. the page says what it says, and what it says is exact 🌸

👑 DESCRIPTION 👑

so the way this works is: RIO_LOP_READ generates the rio_local_read_config_* functions 💫 and those generated functions are the ones you use to access configuration space registers on the local device. local. as in your own device. main character energy, honestly 👑

it doesn't do the read itself — it makes the functions that do. it's giving matchmaker, not the date 💅✨

🌈 SEE ALSO 🌈

• kernel file ./drivers/rapidio/rio-access.c — go read it bestie, it's right there 📂
• RIO_LOP_WRITE(9) — the write-side sibling 🫶
• RIO_OP_READ(9)
• RIO_OP_WRITE(9)
• rio_mport_send_doorbell(9) — yes that's the real name and yes it ate 💅🔔

okay that's the whole page, no gatekeeping 💜 and for the sign-off: this lil masterpiece lives down in ./drivers/rapidio, dated October 2026, and it's filed under RIO_LOP_READ(9) — catch you in the next manpage, bestie, mwah 🎀😭💖