STRUCT INTEL_SPI(9)

💅 struct intel_spi(9)

okay so bestie, welcome to the struct intel_spi page — this is the kernel API manual, and it's literally the driver's own private little data stash. yes, driver private data, that's the whole vibe. it's not public-facing, it's not for you to poke at from userspace, it's just the intel SPI driver keeping its stuff together 🎀

---

✨ NAME ✨

struct intel_spi — driver private data. that's it, that's the whole thing. it holds the driver's own bookkeeping so nobody else has to 😌

---

🌸 SYNOPSIS 🌸

here's the whole struct, exactly as it lives, no cap:

struct intel_spi {
    struct device *dev;
    const struct intel_spi_boardinfo *info;
    void __iomem *base;
    void __iomem *pregs;
    void __iomem *sregs;
    struct spi_controller *host;
    size_t nregions;
    size_t pr_num;
    size_t chip0_size;
    bool locked;
    bool protected;
    bool bios_locked;
    bool swseq_reg;
    bool swseq_erase;
    u8 atomic_preopcode;
    u8 opcodes[8];
    const struct intel_spi_mem_op *mem_ops;
};

like, look at her. organised. iconic. 🫶

---

👑 Members 👑

okay let's go through every single one, because we do not skip members in this house 💖

• dev — the device pointer. your classic "which device am i" situation, honestly every struct has one.
• info — pointer to the board specific info. every board's a little different, bestie, this is where that lives 🦋
• base — the beginning of MMIO space. like the front door of the memory-mapped neighborhood.
• pregs — start of the protection registers. yes, the boring-but-important ones.
• sregs — start of the software sequencer registers. sequencer girlies rise ✨
• host — pointer to the SPI controller structure. she's the main character of the show, fr fr.
• nregions — maximum number of regions. maximum, key word.
• pr_num — maximum number of protected range registers. more maximums, we love a limit 🌸
• chip0_size — size of the first flash chip, in bytes. bytes!! not kilobytes, not vibes. bytes 💀
• locked — is the SPI setting locked. simple bool, big consequences.
• protected — whether the regions are write protected. as in, can't touch, don't even try 🙈
• bios_locked — is the BIOS region locked. yes, that BIOS. the one you should not be messing with.
• swseq_reg — use the SW sequencer in register reads/writes. (SW = software, for the uninitiated 🧚)
• swseq_erase — use the SW sequencer in the erase operation. same energy, different operation.
• atomic_preopcode — holds the preopcode when an atomic sequence is requested. it's a u8, it's little, it's crucial ⭐
• opcodes — the opcodes which are supported. and listen: these are programmed by BIOS before it locks down the controller. read that again if you need to, because it's important — BIOS sets these up, then locks everything, and after that it's hands off 🔥
• mem_ops — pointer to the SPI MEM ops supported by the controller. the controller's lil menu of what it can do, basically.

real talk though — this struct is driver private data. it's the driver's own internal business, so don't go treating it like a public API and building your whole life around the layout, okay? 🎀

---

🌈 SEE ALSO 🌈

go look at these if you want the full picture:

• Kernel file ./drivers/spi/spi-intel.c
• intel_spi_probe(9)

both of those are where the actual lore lives, iykyk 💜

---

aaaand that's the page!! stay slay, stay read-only when the region is write protected, and remember: this blessed manual came from the ./drivers/spi source, dated October 2026. mwah 💋✨