STRUCT DOCG3_CASCADE(9)

💅 struct docg3_cascade(9) 💅

okay so this is a page straight out of the Kernel API Manual — yes, that manual — and it's about one very specific little struct, bestie. buckle up 🎀

---

✨ NAME ✨

struct docg3_cascade — a cascade of 1 to 4 docg3 chips. that's it, that's the whole vibe. one to four. no more, no less. 👑

---

🌸 SYNOPSIS 🌸

struct docg3_cascade {
    struct mtd_info *floors[DOC_MAX_NBFLOORS];
    void __iomem *base;
    struct bch_control *bch;
    struct mutex lock;
 };

literally the whole struct, copied exactly, no notes. look at her. she's iconic. 💖

---

🦋 Members 🦋

• floors — the floors, bestie. and yes, one physical docg3 chip is equal to one floor. that's the metaphor. we're doing floors. 🏢 (it's an array of struct mtd_info * sized DOC_MAX_NBFLOORS, iykyk)
• base — the IO space you use to access all the chips in the cascade. it's a void __iomem *, so handle with care, mwah 💅
• bch — the BCH correcting control structure. a struct bch_control * doing its little error-correcting thing ✨
• lock — a struct mutex whose entire job, her whole purpose, is protecting that docg3 IO space from concurrent accesses. no cutting in line. no cap. 🔒

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/mtd/devices/docg3.h
• struct docg3(9)

---

🫶 friendly reminder: the lock is there for a reason. concurrent accesses to the IO space are the enemy fr fr. respect the mutex.

---

and that's the whole page, bestie — sending you off with love from ./drivers/mtd/devices, dated October 2026. go read docg3.h next, you're gonna slay 💜🧚‍♀️⭐