Lines Matching refs:event

39 Overall these models are "event driven". There is several ways
43 ### About the event scheduling
65 Normally each peripheral model will have 1 of such event timers, and it will
69 Whenever a HW model updates its event timer, it will call a function in the HW scheduler.
72 when needed, and call into the corresponding HW submodule "event|task runner"
73 whenever its event time is reached.
77 Each timer|event has a given priority, and therefore will always be called
80 Note also, that any HW submodule may schedule a new event to be called in the
84 When they do so, their "event|task runner" will be called right after in the
152                                     Use a registered event. When that event timer
155                                     event timer.
159 signal_<event register name>() : Signal that <event> has just happened,
163 The tasks, registers and event names should match the register interface
173 As described before, overall the models are "event driven":
192 These event timers may be changed after each execution of the models, or whenever