STRUCT SCMI_EVENT_HEADER(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, you opened the Kernel API Manual page for struct scmi_event_header(9) and honestly? It's giving β€œsmall but important utility header” energy πŸ’…βœ¨ Stay for the lore, because every member and every SEE ALSO ref is coming with us.

πŸŽ€ NAME πŸŽ€

struct scmi_event_header β€” A utility header. That's the whole vibe: a utility header, no cap.

✨ SYNOPSIS ✨

Here's the exact shape, bestie:

struct scmi_event_header {
    ktime_t timestamp;
    size_t payld_sz;
    unsigned char evt_id;
    unsigned char payld[];
 };

🫢 Members 🫢

Okay squad, member check:

  • timestamp β€” the timestamp, in nanoseconds (boottime), which was associated to this event as soon as it entered the SCMI RX ISR. Literally the event's little arrival receipt πŸ•°οΈ.
  • payld_sz β€” the effective size of the embedded message payload which follows. Like, the real size of the payload that's coming after it.
  • evt_id β€” the event ID (corresponds to the Event MsgID for this Protocol). Capitalization matters, iykyk.
  • payld β€” a reference to the embedded event payload. The payload itself, bestie πŸ’–.

🌸 Description 🌸

This header is prepended to each received event message payload before queueing it on the related struct events_queue. So yes, the header goes in front of the payload before the queueing situation happens β€” very organized, very main character energy ✨.

πŸ”₯ SEE ALSO πŸ”₯

If you want the full group chat, start with the kernel file ./drivers/firmware/arm_scmi/notify.c and Theory of operation(9), then scroll through the whole squad:


mwah πŸ’‹ this page lives under ./drivers/firmware/arm_scmi, dated October 2026, and it's the struct scmi_event_header(9) manual page β€” bye bestie, go slay those events πŸŽ€βœ¨

πŸ“¦ where this page comes from