STRUCT WILCO_EC_MESSAGE(9)

✨ struct wilco_ec_message — Request and response message ✨

okay bestie, so this is a page straight out of the Kernel API Manual, and it's about struct wilco_ec_message — literally the little envelope you use to slide a message over to the EC (embedded controller) and get one back. Think of it as your request-and-response situationship, formalized in C. 💌

🌸 SYNOPSIS 🌸

struct wilco_ec_message {
    enum wilco_ec_msg_type type;
    u8 flags;
    size_t request_size;
    void *request_data;
    size_t response_size;
    void *response_data;
 };

🎀 Members 🎀

• type — the mailbox message type. basically what kind of message you're sending, iykyk.
• flags — message flags, e.g. WILCO_EC_FLAG_NO_RESPONSE. little extra vibes attached to the message.
• request_size — number of bytes to send to the EC. count 'em.
• request_data — buffer containing the request data. this is the payload you're shipping out 🫶
• response_size — number of bytes to read from EC. how much you're expecting back.
• response_data — buffer containing the response data. it should be response_size bytes and allocated by caller — so yes, that's on you, not on the kernel. no cap, do your own mallocing. 💅

heads up bestie: that last one is a classic gotcha. response_data must be allocated by the caller and sized to exactly response_size bytes. don't be out here handing it an unallocated pointer, that's giving undefined chaos. 😭

💜 SEE ALSO 💜

• Kernel file ./include/linux/platform_data/wilco-ec.h
• struct wilco_ec_device(9)
• struct wilco_ec_request(9)
• struct wilco_ec_response(9)
• enum wilco_ec_msg_type(9)
• wilco_ec_mailbox(9)
• wilco_keyboard_leds_init(9)
• wilco_ec_get_property(9)
• wilco_ec_set_property(9)
• wilco_ec_get_byte_property(9)
• wilco_ec_add_sysfs(9)

and that's the whole page, bestie — iconic, no notes. this one's filed under ./include/linux/platform_data and stamped October 2026, so go forth and message your EC responsibly 🦋💖✨