3 Many triggers are provided by hardware that will also be registered as
4 an IIO device. Whilst this can create device specific complexities
5 such triggers are registered with the core in the same way as
8 struct iio_trig *trig = iio_trigger_alloc("<trigger format string>", ...);
10 allocates a trigger structure. The key elements to then fill in within
13 trig->set_trigger_state:
14 Function that enables / disables the underlying source of the trigger.
17 trig->alloc_list which is useful for drivers that allocate multiple
18 triggers to keep track of what they have created.
20 When these have been set call:
22 iio_trigger_register(trig);
24 to register the trigger with the core, making it available to trigger
29 Currently triggers are only used for the filling of software
30 buffers and as such any device supporting INDIO_BUFFER_TRIGGERED has the
31 consumer interface automatically created.