1IIO trigger drivers.
2
3Many triggers are provided by hardware that will also be registered as
4an IIO device.  Whilst this can create device specific complexities
5such triggers are registered with the core in the same way as
6stand-alone triggers.
7
8struct iio_trig *trig = iio_allocate_trigger("<trigger format string>", ...);
9
10allocates a trigger structure.  The key elements to then fill in within
11a driver are:
12
13trig->private_data
14	Device specific private data.
15
16trig->owner
17	Typically set to THIS_MODULE. Used to ensure correct
18	ownership of core allocated resources.
19
20trig->set_trigger_state:
21	Function that enables / disables the underlying source of the trigger.
22
23There is also a
24trig->alloc_list which is useful for drivers that allocate multiple
25triggers to keep track of what they have created.
26
27When these have been set call:
28
29iio_trigger_register(trig);
30
31to register the trigger with the core, making it available to trigger
32consumers.
33
34Trigger Consumers
35
36Currently triggers are only used for the filling of software
37buffers and as such any device supporting INDIO_RING_TRIGGERED has the
38consumer interface automatically created.
39