MVICU(4)

💅 MVICU(4) — like, the Marvell Armada Interrupt Consolidation Unit page, bestie ✨

okay so real talk, this is a section 4 kernel interfaces manual page (yes, the 4 is part of the vibe) and honestly? it's short, it's sweet, and it's giving "small driver, big job." let's get into it 🎀

---

🌸 NAME 🌸

mvicu — the Marvell Armada Interrupt Consolidation Unit, aka the little block that keeps all the interrupts from chaos-ing into each other 🧚

⭐ SYNOPSIS ⭐

mvicu* at fdt?

that's it. that's the whole configuration line. mvicu* matches the device, and at fdt? means it attaches to the device tree, no cap 🫶

💖 DESCRIPTION 💖

so the mvicu driver is the support system for the interrupt controller that's built into the CP110 block of the Marvell Armada 70x0/80x0 SoCs. that's the whole description. it shows up, it holds down the interrupt controller, it does its job. iconic behavior honestly 👑

🦋 SEE ALSO 🦋

• intro(4) — the intro page for section 4, go say hi, iykyk 🌈

🕰️ HISTORY 🕰️

the mvicu driver first appeared in OpenBSD 6.4. a whole era, fr fr 💜

👑 AUTHORS 👑

the mvicu driver was written by Mark Kettenis <kettenis@openbsd.org>. we stan a kernel-writing legend, genuinely 💅✨

also like… if you're gonna email him, be normal about it please 🫶

💀 BUGS 💀

okay so this is the one you gotta know about: the mvicu driver relies on the hardware being initialized by the firmware. like, it does not do the setup itself, it trusts the firmware to have handled that already. so if things are weird, that's the vibe check that failed 😭

---

and that's the whole page, bestie — short king energy from start to finish 🍓

this one came from the Debian build dated March 31, 2018, and yes the page header and footer literally both say MVICU(4) because that's just how manpages do 🌸 stay consolidated, stay interrupt-free 💖

---