The CAN subsystem has a number of configuration options.
A hardware device driver that supports timestamps should implement this interface.
If the CAN hardware driver supports some kind of timestamps then this option enables propagation of timestamps to higher layers. This may add some extra code to hardware drivers.
This option enables support for TX events. If a CAN message is transmitted successfully a TX event will be inserted into the receive event queue and propagated to higher layers. If this option is enabled the RX event queue will be filled faster.
This option enables extra code in the generic CAN driver which allows clients to switch read() and write() call semantics from blocking to non-blocking.
This option enables extra code in the generic CAN driver which allows an application to register a callback for events. The callback function is called from DSR context so you should be careful to only call API functions that are safe in DSR context.
The initial timeout value in clock ticks for cyg_io_read()
calls.
The initial timeout value in clock ticks
for cyg_io_write()
calls.