STRUCT RMI_FUNCTION_HANDLER(9)

✨ struct rmi_function_handler(9) ✨

okay so bestie, welcome to the struct rmi_function_handler glow-up 💅 this is a Kernel API Manual situation, and it's literally the driver routines for a particular RMI function — like, one function, one handler, main character energy only 👑

---

🌸 NAME 🌸

struct rmi_function_handler — driver routines for a particular RMI function, periodt.

---

🎀 SYNOPSIS 🎀

struct rmi_function_handler {
    struct device_driver driver;
    u8 func;
    int (*probe)(struct rmi_function *fn);
    void (*remove)(struct rmi_function *fn);
    int (*config)(struct rmi_function *fn);
    int (*reset)(struct rmi_function *fn);
    irqreturn_t (*attention)(int irq, void *ctx);
    int (*suspend)(struct rmi_function *fn);
    int (*resume)(struct rmi_function *fn);
 };

no cap, that's the whole struct, copy it exactly, don't get creative with it 🙈

---

🦋 Members 🦋

so here's the cast of callbacks, and honestly? every one of them ate:

• func — the RMI function number. that's it, that's the whole vibe check 🎀
• config — gets called when the function container is first initialized, and again after a reset is detected. this routine should write any necessary configuration settings to the device. basically: set it up, then set it up again if the world ends 💖
• reset — called when a reset of the touch sensor is detected. this routine should perform any out-of-the-ordinary reset handling that might be necessary. and lowkey important: restoring of touch sensor configuration registers should be handled in the config callback, below. not here. iykyk 🫶
• attention — called when the IRQ(s) for the function are set by the touch sensor. she's the one who answers the phone ☎️✨
• suspend — should perform any required operations to suspend the particular function 😴
• resume — should perform any required operations to resume the particular function 🌞

ngl bestie, probe and remove are right there in the struct too — they're part of the whole package even though this list doesn't give them their own lil paragraph 🙈

---

⭐ Description ⭐

all callbacks are expected to return 0 on success, error code on failure. that's the rule, no exceptions, fr fr 🔥

---

🍓 SEE ALSO 🍓

• Kernel file ./drivers/input/rmi4/rmi_bus.h struct rmi_function(9)
• rmi_reset(9)
• rmi_read(9)
• rmi_read_block(9)
• rmi_write(9)
• rmi_write_block(9)

go read those, they're iconic 👑

---

and that's the page!! courtesy of ./drivers/input/rmi4, dated October 2026, and yes she's still signing off as struct rmi_function_handler(9) because consistency is a love language 💜🌷