STRUCT MCFQSPI_CS_CONTROL(9)

💅 struct mcfqspi_cs_control(9) 💅

okay so bestie, we're in the Kernel API Manual today and the star of the show is struct mcfqspi_cs_control — literally the chip select control for the coldfire qspi driver. she's small, she's iconique, she has function pointers. let's get into it 🎀

---

✨ SYNOPSIS ✨

struct mcfqspi_cs_control {
    int (*setup)(struct mcfqspi_cs_control *);
    void (*teardown)(struct mcfqspi_cs_control *);
    void (*select)(struct mcfqspi_cs_control *, u8, bool);
    void (*deselect)(struct mcfqspi_cs_control *, u8, bool);
 };

no cap, that's the whole struct. four pointers and a dream 🦋

---

🌸 Members 🌸

• setup — sets up the control: allocates the gpio's, etc. she may be NULL, so don't come for her if she ghosts you. 🙈
• teardown — finishes up with the control: frees the gpio's, etc. also allowed to be NULL. lowkey the responsible one. 🧹
• select — outputs the signals that select the device. can not be NULL — this one is required, periodt. 🔥
• deselect — outputs the signals that deselect the device. can not be NULL either. two absolutely non-negotiable icons. 👑

---

💖 Description 💖

so here's the tea ☕ the QSPI module has 4 hardware chip selects. we don't use them. i know, i know — four whole chip selects just sitting there, and we said "nah." 💀

instead, platforms are required to supply a mcfqspi_cs_control as a part of the platform data for each QSPI master controller. that's the vibe check: bring your own cs control, one per master controller.

and the only functions that are actually required are select and deselect. setup and teardown? optional, bestie. everything else? mandatory. iykyk 🫶

---

🦋 SEE ALSO 🦋

• Kernel file ./arch/m68k/include/asm/mcfqspi.h — struct
• mcfqspi_platform_data(9)

---

and that's the whole page, bestie — no notes, she ate. 💅

anyway, source tease: this came out of ./arch/m68k/include/asm, dated October 2026, page struct mcfqspi_cs_control(9). mwah, stan. 🍓🎀💜