STRUCT K3_RPROC_MEM(9)

💅 struct k3_rproc_mem(9) — internal memory structure

okay so bestie, welcome to struct k3_rproc_mem(9) from the Kernel API Manual ✨ this is lowkey one of those little structs that just holds memory info and honestly? it ate. it's an internal memory structure and it's giving "quiet supporting character who's actually the main character" energy 🎀

✨ SYNOPSIS ✨

like, here's the whole vibe, verbatim, don't touch it:

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

that's it. four fields. no cap, she's compact 🦋

🌸 Members 🌸

each member is a different flavor of "where does this memory even live" and i'm obsessed:

• cpu_addr — the MPU virtual address of the memory region 💻 like, this is where your CPU sees it, the void __iomem * situation.
• bus_addr — the bus address used to access the memory region 🚌 this is the address the bus deals with when it wants in.
• dev_addr — the device address of the memory region from the remote processor's point of view 👀 yes, from their perspective — remote processor POV, iykyk.
• size — size of the memory region 📏 a size_t, obviously. it tells you how much memory we're talking about.

fr fr, every field is just a different address-y way of pointing at the same region — cpu view, bus view, remote-proc view, plus how big it is. that's the whole arc 💖

🫶 SEE ALSO 🫶

go read these next, bestie, they're the friend group:

• Kernel file ./drivers/remoteproc/ti_k3_common.h struct k3_rproc_mem_data(9), struct k3_rproc_dev_data(9), struct k3_rproc(9)

and that's the page!! 🌈 this was ./drivers/remoteproc, October 2026, struct k3_rproc_mem(9) — go forth and slay your address translations, periodt 💅🔥