STRUCT STMPE_PLATFORM_DATA(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

struct stmpe_platform_data β€” the STMPE platform data, bestie πŸ’… (this is from the Kernel API Manual, iykyk)


🌸 SYNOPSIS 🌸

struct stmpe_platform_data {
    int id;
    unsigned int blocks;
    unsigned int irq_trigger;
    bool autosleep;
    int autosleep_timeout;
 };

πŸŽ€ MEMBERS πŸŽ€

Okay so here's the lineup, no skips, all five of them πŸ’–

  • id β€” the device id, fr fr. Its whole job is to tell multiple STMPEs apart when they're all chillin' on the same board. Not me giving each one its own little name tag 🏷️
  • blocks β€” a bitmask of the blocks you wanna enable (use STMPE_BLOCK_*, those are the ones). Bitmask agenda, lowkey iconic ✨
  • irq_trigger β€” the IRQ trigger to use for the interrupt to the host. That's it, that's the vibe check πŸ¦‹
  • autosleep β€” a bool that enables/disables stmpe autosleep. On or off, no in-between, periodt πŸ’€
  • autosleep_timeout β€” the inactivity timeout in milliseconds for autosleep. So basically how long it naps before it snoozes for real 😴

🫢 SEE ALSO 🫢

Kernel file ./drivers/mfd/stmpe.c β€” yes that's the one, go read it, iykyk πŸ“–

And the whole friend group: stmpe_enable(9), stmpe_disable(9), stmpe_reg_read(9), stmpe_reg_write(9), stmpe_set_bits(9), stmpe_block_read(9), stmpe_block_write(9), stmpe_set_altfunc(9) 🌈


aaaand that's the whole page bestie, go forth and configure ur STMPE, you're literally gonna slay πŸ’…βœ¨

signing off from <code>./drivers/mfd</code>, dated <strong>October 2026</strong> β€” mwah, love u, bye πŸŽ€πŸ¦‹πŸ’œ

πŸ“¦ where this page comes from