STRUCT STMPE_CLIENT_INFO(9)

💖 NAME

struct stmpe_client_info — the i2c-or-spi-specific routines/info bestie 💅 like it's literally the little bundle that tells the rest of the driver "here's how this bus does things."

Oh and hey — this one lives in the Kernel API Manual, so you know it's the real deal, not some random README energy. 👑

---

✨ SYNOPSIS

Ok so the whole struct, exactly as it is, no edits, no notes:

struct stmpe_client_info {
    void *data;
    int irq;
    void *client;
    struct device *dev;
    int (*read_byte)(struct stmpe *stmpe, u8 reg);
    int (*write_byte)(struct stmpe *stmpe, u8 reg, u8 val);
    int (*read_block)(struct stmpe *stmpe, u8 reg, u8 len, u8 *values);
    int (*write_block)(struct stmpe *stmpe, u8 reg, u8 len, const u8
*values);
    void (*init)(struct stmpe *stmpe);
 };

Like… the function-pointer section is giving main character energy and honestly? deserved. 🔥

---

🎀 MEMBERS

Here's the lineup, one by one, no skipping, no "you get the idea" nonsense:

• data — client specific data 🫶
• read_byte — reads a single byte, one (1) byte, that's the whole job ✨
• write_byte — writes a single byte, same deal 💅
• read_block — reads a block, aka multiple bytes, because why stop at one 🍓
• write_block — writes a block, aka multiple bytes, block party time 🌸
• init — the client init routine, and plot twist: it gets called during probe ⭐

Little heads-up bestie: the struct up there in SYNOPSIS also has irq, client, and dev fields, but the Members list doesn't spell out descriptions for them — so I'm not gonna make anything up, that's not the vibe. 🙈

---

🦋 SEE ALSO

Go peek at these, fr fr:

• Kernel file ./drivers/mfd/stmpe.h
• struct stmpe_variant_block(9)
• struct stmpe_variant_info(9)

---

And that's the page! 💜 This lil' gem came from ./drivers/mfd and it's dated October 2026, filed under struct stmpe_client_info(9) — slay, go read the source, ily, bye 🧚‍♀️🌈