STRUCT SCMI_EVENT(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ 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 cap
  • max_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.h struct
  • 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