STRUCT KEYSTONE_RPROC_MEM(9)

💖 struct keystone_rproc_mem(9) 💖

okay so bestie, welcome to the struct keystone_rproc_mem(9) page from the Kernel API Manual — yes that's the manual name, we're being fancy today ✨ this is the little struct that holds all the internal memory bookkeeping for the keystone remoteproc driver, and honestly? she's doing a lot with only four fields. icon.

---

🌸 NAME 🌸

struct keystone_rproc_mem — the internal memory structure, aka the receipts for one chunk of memory. no cap, that's literally her whole job 🎀

---

✨ SYNOPSIS ✨

here's the shape of her, exactly, don't touch the formatting, she's perfect:

struct keystone_rproc_mem {
    void __iomem *cpu_addr;
    phys_addr_t bus_addr;
    u32 dev_addr;
    size_t size;
 };

four members, zero filler, main character energy 💅

---

🦋 Members 🦋

• cpu_addr — the MPU virtual address of the memory region. this is the address we (the MPU) use when we want to poke at it, void __iomem * and all 🫶
• bus_addr — the bus address used to access the memory region. different address, same memory, it's giving "same girl different outfit" 😭 it's a phys_addr_t.
• dev_addr — the device address of the memory region, but from the DSP's point of view 👀 so when the DSP looks at this memory it sees this address. a u32, keep that in mind bestie.
• size — the size of the memory region. a size_t. yes. that's it. that's the field. sometimes the simplest ones ate 💀

lowkey the whole point here: three different addresses for the same region (CPU view, bus view, DSP view) plus a size. if you mix them up, that's on you, not on her 🙈

---

🔥 SEE ALSO 🔥

• the kernel file ./drivers/remoteproc/keystone_remoteproc.c — go read the source, iykyk ⭐
• struct keystone_rproc(9) — her bestie, the big one 👑

---

and that's the page!! remember everything above was served to you straight from ./drivers/remoteproc in October 2026 — so when you cite her, cite her right, mwah 💜🧚🍓