Expand description
Oxide system events; these are generated by the low-level device driver
interrupt handlers and passed to the OxideSupervisor, which is
responsible for then scheduling the appropriate userland code callbacks
to handle the events.
You will not normally need to deal directly with such events from within
an application, rather use the various on_event() style callback
methods provided by the device drivers.
The exception would be when using a pre_handler with avr_oxide::oxide::OxideSupervisor.
See the relevant documentation for examples.
Structs§
- A ‘null’ event sunk that allows you to instantiate Oxide devices that discard any generated events.
- An envelope with a recipient address that we can wrap up Oxide events in.
Enums§
- Events that can cause your application to wake up and need to do something.
Traits§
- An event sink is something that devices can call to dump their events into.
- An event source is something which generates events for later processing.