STRUCT PRU_RPROC(9)

💜 struct pru_rproc — the Kernel API Manual moment

okay so bestie, welcome to the struct pru_rproc(9) page ✨ this is from the Kernel API Manual and it's literally the whole personality of the PRU remoteproc structure. one struct. so many fields. we're gonna get through it together, no cap 🫶

---

🎀 NAME 🎀

struct pru_rproc — the PRU remoteproc structure, aka the main character of this whole page 👑

---

✨ SYNOPSIS ✨

here's the whole glow-up, verbatim, don't touch a single character bestie:

struct pru_rproc {
    int id;
    struct device *dev;
    struct pruss *pruss;
    struct rproc *rproc;
    const struct pru_private_data *data;
    struct pruss_mem_region mem_regions[PRU_IOMEM_MAX];
    struct device_node *client_np;
    struct mutex lock;
    const char *fw_name;
    unsigned int *mapped_irq;
    struct pru_irq_rsc *pru_interrupt_map;
    size_t pru_interrupt_map_sz;
    spinlock_t rmw_lock;
    u32 dbg_single_step;
    u32 dbg_continuous;
    u8 evt_count;
    u8 gpmux_save;
 };

---

🌸 Members 🌸

okay now the vibe check on every single field, one by one, because we do not skip 💅

• id — the id of the PRU core within the PRUSS 🆔
• dev — the PRU core device pointer, it's giving device energy
• pruss — back-reference to the parent PRUSS structure, like a link back to the parent account fr fr
• rproc — the remoteproc pointer for this PRU core, iconic
• data — PRU core specific data, each core's own little lore
• mem_regions — data for each of the PRU memory regions, all of them, plural, we love a collection 💖
• client_np — the client device node 🌈
• lock — a mutex to protect client usage, do not skip the lock bestie, it's literally there to save you 😭
• fw_name — name of the firmware image used during loading, like a contact name but for firmware
• mapped_irq — virtual interrupt numbers of created fw specific mapping
• pru_interrupt_map — pointer to interrupt mapping description (firmware) 🦋
• pru_interrupt_map_sz — the pru_interrupt_map size, the lil sibling field
• rmw_lock — lock for read, modify, write operations on registers, protecting the register glow-up one step at a time ✨
• dbg_single_step — debug state variable to set PRU into single step mode 🐾
• dbg_continuous — debug state variable to restore PRU execution mode, the un-single-step, the comeback arc
• evt_count — number of mapped events
• gpmux_save — saved value for gpmux config 💾

---

🔥 SEE ALSO 🔥

go read these next bestie, iykyk:

• Kernel file ./drivers/remoteproc/pru_rproc.c
• enum pru_iomem(9)
• struct pru_private_data(9)
• pru_rproc_set_firmware(9)
• pru_rproc_get(9)
• pru_rproc_put(9)
• pru_rproc_set_ctable(9)

---

that's the whole page bestie, you ate that 🍓 and for the credits moment: this one lives at ./drivers/remoteproc, from the October 2026 Kernel API Manual, and it's literally signed struct pru_rproc(9) at the bottom like a little autograph 💜 mwah, go read the source, you're gonna slay 🧚