STRUCT SCMI_EVENT(9)
β¨ struct scmi_event(9) β¨
okay so bestie, welcome to the Kernel API Manual entry for struct scmi_event(9) β yes the whole page is named after the struct, that's just how these things roll π
π NAME π
struct scmi_event β literally just Describes an event to be supported π¦
πΈ SYNOPSIS πΈ
struct scmi_event {
u8 id;
size_t max_payld_sz;
size_t max_report_sz;
};
that's the whole vibe. three fields. no notes. iconic β¨
π Members π
idβ Event ID π (that's it, that's the field)max_payld_szβ Max possible size for the payload of a notification message π¦ like, the biggest it could ever be, no capmax_report_szβ Max possible size for the report of a notification message π¨ same deal but for the report
π₯ Description π₯
so here's the tea β β every SCMI protocol, during its initialization phase, can describe the events it wishes to support in a few struct scmi_event and pass them to the core using scmi_register_protocol_events.
that's it. that's the whole lore. the protocol shows up, says "these are my events bestie," hands over a few structs, and the core takes it from there π«Ά no extra steps, no drama, just registration main character energy π
π SEE ALSO π
- Kernel file
./drivers/firmware/arm_scmi/notify.hstruct scmi_event_ops(9)struct scmi_protocol_events(9)
and that's the page!! go read those other structs too, they're lowkey obsessed with each other iykyk π§π
source/version: ./drivers/firmware/arm_scmi Β· dated October 2026 β mwah, catch u in the next manpage, bestie π
πβ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms