STRUCT ZYNQ_QSPI(9)

📦 version 7.3.1, in nixpkgs unstable

💜 struct zynq_qspi(9) — bestie edition

okay so this is a page straight out of the Kernel API Manual, and it's literally the blueprint for a QSPI driver instance. no cap, it's just the struct definition, but it's iconic.

✨ NAME ✨

struct zynq_qspi — defines the qspi driver instance. that's it, that's the whole vibe 🎀

🌸 SYNOPSIS 🌸

here's the shape of it, copied exactly so you don't have to squint at a screenshot:

struct zynq_qspi {
    struct device *dev;
    void __iomem *regs;
    struct clk *refclk;
    struct clk *pclk;
    int irq;
    u8 *txbuf;
    u8 *rxbuf;
    int tx_bytes;
    int rx_bytes;
    struct completion data_completion;
 };

🦋 Members 🦋

okay bestie, field-by-field tour, let's go 💅

  • dev — pointer to this device's information. like, whose device is this even? this pointer knows 👑
  • regs — the virtual address of the QSPI controller registers. virtual, not physical, don't get it twisted ✨
  • refclk — pointer to the peripheral clock. it's giving timing, it's giving rhythm 🕺
  • pclk — pointer to the APB clock. yes, there are two clocks, and yes, they're both important 🫶
  • irq — the IRQ number. interrupts said hi 😭
  • txbuf — pointer to the TX buffer. where the outgoing gossip lives 📤
  • rxbuf — pointer to the RX buffer. where the incoming gossip lands 📥
  • tx_bytes — number of bytes left to transfer. left, as in still pending, not total, okay? important 💀
  • rx_bytes — number of bytes left to receive. same deal, still-on-the-way energy ⭐
  • data_completion — a completion structure. it's literally there to tell you when the data situation is handled 🌈

🔥 SEE ALSO 🔥

lowkey the whole friend group is in that list — go read them next, iykyk 💖

and that's the page, bestie!! 🧚 this one came from ./drivers/spi, dated October 2026, filed under struct zynq_qspi(9) in the Kernel API Manual — go off and write something slay with it 💅✨🍓

📦 where this page comes from