STRUCT VPU(9)

✨ struct vpu ✨

okay so this is a page from the Kernel API Manual (section 9, struct vpu(9) — yes bestie, section nine, we're in kernel-internals territory 💅) and it's literally just the tea on struct vpu, which is the Ingenic VPU remoteproc private structure. that's it, that's the whole vibe. she's private, she's Ingenic, she's a VPU, she keeps her business to herself 🫶

---

🌸 NAME 🌸

struct vpu — the Ingenic VPU remoteproc private structure. no cap, that's the name and the whole personality.

---

🎀 SYNOPSIS 🎀

here's the actual shape of her, character for character, do not touch:

struct vpu {
    int irq;
    struct clk_bulk_data clks[2];
    void __iomem *aux_base;
    struct vpu_mem_info mem_info[ARRAY_SIZE(vpu_mem_map)];
    struct device *dev;
 };

like, look at that. five members. she's compact. she's iconic. she ate and left zero crumbs 🔥

---

💅 Members 💅

okay now we get into the individual members, and honestly this is the part where i need you to lock in bestie, because these are the facts and the facts are not changing:

• irq — the interrupt number. that's it. that's her whole job. one little int holding the interrupt number 🦋
• clks — pointers to the VPU and AUX clocks. it's a struct clk_bulk_data, and note that it's clks[2] — two of them, because there are two clocks (VPU and AUX, as established). two clocks, two slots, math is mathing 💜
• aux_base — a raw pointer to the AUX interface registers. it's void __iomem *, so it's raw and it's memory-mapped, and we respect that. register poking happens here, iykyk ✨
• mem_info — an array of struct vpu_mem_info, which contain the mapping info of each of the external memories. and it's sized as ARRAY_SIZE(vpu_mem_map), so the size comes straight from vpu_mem_map, not from a hardcoded number. one entry per external memory, all mapped out, organized queen 👑
• dev — a private pointer to the device. private. pointer. device. the link back to the big struct device. she's got connections 🌈

---

🔍 SEE ALSO 🔍

if you want the actual source (and honestly, why wouldn't you), it lives in the Kernel file:

./drivers/remoteproc/ingenic_rproc.c

that's the spot. go read it, it's giving main character energy 🧚

---

and that's the page bestie 🎀 nothing dangerous here, no deprecated flags, no undefined behaviour, just five struct members and a clock array of exactly two. keep the details exact and slay responsibly 💖

---

sign-off time 🌸 this page came out of ./drivers/remoteproc and it's dated October 2026 — so like, future-dated, very ahead of its time, absolutely iconic of her. mwah 💋