STRUCT RAVE_SP_VARIANT_CMDS(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct rave_sp_variant_cmds(9) β€” bestie edition πŸŽ€

okay so picture this: it's the Kernel API Manual, section 9, and the star of the show is struct rave_sp_variant_cmds β€” literally the place where all the variant specific command routines live. like, every board wants to do its own lil thing and this struct is the vibe check that makes it happen ✨


🌸 NAME 🌸

struct rave_sp_variant_cmds β€” Variant specific command routines πŸ¦‹

that's it, that's the whole name. short, iconic, main character energy πŸ‘‘


✨ SYNOPSIS ✨

here's the whole shape of it, no cap, copy it exactly bestie:

struct rave_sp_variant_cmds {
    int (*translate)(enum rave_sp_command);
    int (*get_status)(struct rave_sp *sp, struct rave_sp_status *);
 };

two function pointers, zero drama, highkey perfect πŸ’–


🫢 Members 🫢

  • translate β€” the generic to variant specific command mapping routine πŸ”₯ like, you hand it a generic command and it tells you what the variant actually wants to do with it. a little translator bestie for your commands, iykyk 🌈
  • get_status β€” the variant specific implementation of CMD_GET_STATUS πŸ’… yes queen, each variant gets to roll its own status-checking logic and honestly? obsessed πŸ“

πŸ‘‘ SEE ALSO πŸ‘‘

go read these next, fr fr β€” first up the Kernel file ./drivers/mfd/rave-sp.c 🧚 and then the whole friend group:

  • enum rave_sp_deframer_state(9)
  • struct rave_sp_deframer(9)
  • struct rave_sp_reply(9)
  • struct rave_sp_checksum(9)
  • struct rave_sp_variant(9)
  • struct rave_sp(9)

all of them slay in their own way, go say hi πŸ’œ


and that's the page πŸŽ€ huge shoutout to ./drivers/mfd for being the source, and to October 2026 for the date stamp β€” periodt, end of manual, mwah πŸ’‹πŸ’–

πŸ“¦ where this page comes from