STRUCT OCELOT_DDATA(9)

🦋 struct ocelot_ddata(9) 🦋

okay bestie, welcome to the Kernel API Manual 💖 this page is all about struct ocelot_ddata, aka the private data for an external Ocelot chip. it’s giving very specific little struct energy, and honestly? we’re obsessed ✨

💖 NAME 💖

struct ocelot_ddata — private data for an external Ocelot chip. that’s the whole name section, bestie, short and iconic 🎀

✨ SYNOPSIS ✨

struct ocelot_ddata {
    struct regmap *gcb_regmap;
    struct regmap *cpuorg_regmap;
    int spi_padding_bytes;
    void *dummy_buf;
 };

👑 Members 👑

• gcb_regmap — this is the General Configuration Block regmap, bestie. it’s used for operations like chip reset. very main character of it 💅
• cpuorg_regmap — the CPU Device Origin Block regmap. used for operations like SPI bus configuration. slay 🔥
• spi_padding_bytes — the number of padding bytes that must be thrown out before read data gets returned. this is calculated during initialization based on bus speed, no cap 🌸
• dummy_buf — a zero-filled buffer of spi_padding_bytes size. it’s literally the dummy bytes that will be sent out between the address and data of a SPI read operation 🫶

🌈 SEE ALSO 🌈

• Kernel file ./drivers/mfd/ocelot.h — go look, iykyk 👀

okay that’s the whole vibe 💜 this page came from ./drivers/mfd, dated October 2026, and it’s the struct ocelot_ddata(9) manual. mwah, go forth and configure responsibly 🧚‍♀️🎀