scmi_lookup_..._event_chain(9)

💅 NAME

okay so this is scmi_lookup_..._event_chain(9) from the Kernel API Manual, and the actual function name is scmi_lookup_and_call_event_chain — literally lookup the proper chain and call it. That’s the whole vibe, bestie. ✨

🌸 SYNOPSIS

void scmi_lookup_and_call_event_chain (struct scmi_notify_instance *ni ,
       u32 evt_key , void *report );

🎀 ARGUMENTS

• ni — a reference to the notification instance to use. like, the notification instance you’re rolling with 💖
• evt_key — the key to use to lookup the related notification chain 🔑
• report — the customized event-specific report to pass down to the callbacks as their *data parameter. yes, *data exactly, no cap 🫶

🦋 SEE ALSO

the whole friend group, fr fr:

• Kernel file ./drivers/firmware/arm_scmi/notify.c Theory of operation(9) — the theory-of-operation lore
• struct scmi_notify_instance(9)
• struct events_queue(9)
• struct scmi_event_header(9)
• struct scmi_registered_events_desc(9)
• struct scmi_registered_event(9)
• struct scmi_event_handler(9)
• scmi_process_event_header(9)
• scmi_process_event_payload(9)
• scmi_events_dispatcher(9)
• scmi_notify(9)
• scmi_kfifo_free(9)
• scmi_initialize_events_queue(9)
• scmi_allocate_registered_events_desc(9)
• scmi_register_protocol_events(9)
• scmi_deregister_protocol_events(9)
• scmi_allocate_event_handler(9)
• scmi_free_event_handler(9)
• scmi_bind_event_handler(9)
• scmi_valid_pending_handler(9)
• scmi_register_event_handler(9)
• __scmi_event_handler_get_ops(9)
• scmi_get_active_handler(9)
• __scmi_enable_evt(9)
• scmi_put_handler_unlocked(9)
• scmi_event_handler_enable_events(9)
• scmi_notifier_register(9)
• scmi_notifier_unregister(9)
• scmi_devm_notifier_register(9)
• scmi_devm_notifier_unregister(9)
• scmi_protocols_late_init(9)
• scmi_notification_init(9)
• scmi_notification_quiesce(9)
• scmi_notification_exit(9)

okay bye bestie 💖 this page is from the Kernel API Manual, source ./drivers/firmware/arm_scmi, dated October 2026 — iconic, periodt. 🌈