ENUM WILCO_EC_MSG_TYPE(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– enum wilco_ec_msg_type β€” the Kernel API Manual, bestie edition πŸ’–

okay so this is enum wilco_ec_msg_type, and it's literally the thing that tells the EC which flavor of command codes you're about to speak. like, it picks the whole lane you're driving in. one enum, three vibes, zero drama. ✨

🌸 SYNOPSIS 🌸

enum wilco_ec_msg_type {
    WILCO_EC_MSG_LEGACY ,
    WILCO_EC_MSG_PROPERTY ,
    WILCO_EC_MSG_TELEMETRY

};

that's the whole shape of it β€” three constants, in that order, and yes the trailing comma after WILCO_EC_MSG_TELEMETRY is just there living its life. πŸ’…

πŸŽ€ Constants (the main characters) πŸŽ€

  • WILCO_EC_MSG_LEGACY β€” the og messages. these are the legacy EC messages for standard EC behavior, aka the classic stuff the EC has always done. vintage, but functional. πŸ‘‘
  • WILCO_EC_MSG_PROPERTY β€” for when you're doing Get/Set/Sync on an EC controlled NVRAM property. yes bestie, NVRAM properties, we love a persistent vibe check. πŸ¦‹
  • WILCO_EC_MSG_TELEMETRY β€” this one's the gossip girl of the enum: it requests telemetry data from the EC. it's giving "spill the data, i'm listening." πŸ”₯

🌈 SEE ALSO 🌈

the kernel file to go look at is ./include/linux/platform_data/wilco-ec.h (that's where all the lore lives). and then, in no particular order, the whole friend group:

like, go read all of them, they're iconic, i promise. 🫢


ngl bestie, this page is short but that's the point β€” pick your message type, send your message, slay. no cap. πŸ’œ

okay so that's a wrap! this one lives under ./include/linux/platform_data, and it's dated October 2026 β€” so yes, it's a little time traveler from the future, we stan a forward-thinking manpage. catch you in the next one, mwah! πŸŒΈπŸ’–πŸŽ€β­πŸ˜­πŸ“

πŸ“¦ where this page comes from