Lines Matching full:protocols
61 * different protocols while delivery of events within the same protocol is
144 * populated at protocols' registration time and then only read but NEVER
178 /* A couple of utility macros to limit cruft when calling protocols' helpers */
287 * All protocols that register at least one event have their protocol-specific
293 * removed or modified since protocols do not unregister ever, so that, once
332 * removed or modified since protocols do not unregister ever, so that once we
530 * flood of events cannot saturate other protocols' queues.
533 * + all protocols can process their dedicated queues concurrently
704 /* Ensure protocols are up to date */ in scmi_allocate_registered_events_desc()
746 * Used by SCMI Protocols initialization code to register with the notification
841 /* Ensure protocols are updated */ in scmi_register_protocol_events()
874 /* Ensure protocols are updated */ in scmi_deregister_protocol_events()
958 * Acquire protocols only for NON pending handlers, so as NOT to trigger in scmi_bind_event_handler()
961 * protocols for which still no SCMI driver user exists: they wouldn't in scmi_bind_event_handler()
982 * protocols register their supported events once for all at protocols'
1590 /* Ensure protocols and events are up to date */ in scmi_protocols_late_init()
1640 * SCMI Protocols can register their events with the core during their own
1644 * cause the whole SCMI Protocols stack to fail its initialization.
1648 * * registration: protocols asynchronously come into life and registers their
1655 * This allows for lazy initialization of SCMI Protocols due to late (or