1 ======== 1 ========
2 Triggers 2 Triggers
3 ======== 3 ========
4 4
5 * struct iio_trigger — industrial I/O trigge !! 5 * struct :c:type:`iio_trigger` — industrial I/O trigger device
6 * :c:func:`devm_iio_trigger_alloc` — Resourc 6 * :c:func:`devm_iio_trigger_alloc` — Resource-managed iio_trigger_alloc
>> 7 * :c:func:`devm_iio_trigger_free` — Resource-managed iio_trigger_free
7 * :c:func:`devm_iio_trigger_register` — Reso 8 * :c:func:`devm_iio_trigger_register` — Resource-managed iio_trigger_register
>> 9 * :c:func:`devm_iio_trigger_unregister` — Resource-managed
8 iio_trigger_unregister 10 iio_trigger_unregister
9 * :c:func:`iio_trigger_validate_own_device` †11 * :c:func:`iio_trigger_validate_own_device` — Check if a trigger and IIO
10 device belong to the same device 12 device belong to the same device
11 13
12 In many situations it is useful for a driver t 14 In many situations it is useful for a driver to be able to capture data based
13 on some external event (trigger) as opposed to 15 on some external event (trigger) as opposed to periodically polling for data.
14 An IIO trigger can be provided by a device dri 16 An IIO trigger can be provided by a device driver that also has an IIO device
15 based on hardware generated events (e.g. data 17 based on hardware generated events (e.g. data ready or threshold exceeded) or
16 provided by a separate driver from an independ 18 provided by a separate driver from an independent interrupt source (e.g. GPIO
17 line connected to some external system, timer 19 line connected to some external system, timer interrupt or user space writing
18 a specific file in sysfs). A trigger may initi 20 a specific file in sysfs). A trigger may initiate data capture for a number of
19 sensors and also it may be completely unrelate 21 sensors and also it may be completely unrelated to the sensor itself.
20 22
21 IIO trigger sysfs interface 23 IIO trigger sysfs interface
22 =========================== 24 ===========================
23 25
24 There are two locations in sysfs related to tr 26 There are two locations in sysfs related to triggers:
25 27
26 * :file:`/sys/bus/iio/devices/trigger{Y}/*`, t 28 * :file:`/sys/bus/iio/devices/trigger{Y}/*`, this file is created once an
27 IIO trigger is registered with the IIO core 29 IIO trigger is registered with the IIO core and corresponds to trigger
28 with index Y. 30 with index Y.
29 Because triggers can be very different depen 31 Because triggers can be very different depending on type there are few
30 standard attributes that we can describe her 32 standard attributes that we can describe here:
31 33
32 * :file:`name`, trigger name that can be lat 34 * :file:`name`, trigger name that can be later used for association with a
33 device. 35 device.
34 * :file:`sampling_frequency`, some timer bas 36 * :file:`sampling_frequency`, some timer based triggers use this attribute to
35 specify the frequency for trigger calls. 37 specify the frequency for trigger calls.
36 38
37 * :file:`/sys/bus/iio/devices/iio:device{X}/tr 39 * :file:`/sys/bus/iio/devices/iio:device{X}/trigger/*`, this directory is
38 created once the device supports a triggered 40 created once the device supports a triggered buffer. We can associate a
39 trigger with our device by writing the trigg !! 41 trigger with our device by writing the trigger's name in the
40 :file:`current_trigger` file. 42 :file:`current_trigger` file.
41 43
42 IIO trigger setup 44 IIO trigger setup
43 ================= 45 =================
44 46
45 Let's see a simple example of how to setup a t 47 Let's see a simple example of how to setup a trigger to be used by a driver::
46 48
47 struct iio_trigger_ops trigger_ops = { 49 struct iio_trigger_ops trigger_ops = {
48 .set_trigger_state = sample_trigger_ 50 .set_trigger_state = sample_trigger_state,
49 .validate_device = sample_validate_d 51 .validate_device = sample_validate_device,
50 } 52 }
51 53
52 struct iio_trigger *trig; 54 struct iio_trigger *trig;
53 55
54 /* first, allocate memory for our trigge 56 /* first, allocate memory for our trigger */
55 trig = iio_trigger_alloc(dev, "trig-%s-% 57 trig = iio_trigger_alloc(dev, "trig-%s-%d", name, idx);
56 58
57 /* setup trigger operations field */ 59 /* setup trigger operations field */
58 trig->ops = &trigger_ops; 60 trig->ops = &trigger_ops;
59 61
60 /* now register the trigger with the IIO 62 /* now register the trigger with the IIO core */
61 iio_trigger_register(trig); 63 iio_trigger_register(trig);
62 64
63 IIO trigger ops 65 IIO trigger ops
64 =============== 66 ===============
65 67
66 * struct iio_trigger_ops — operations struct !! 68 * struct :c:type:`iio_trigger_ops` — operations structure for an iio_trigger.
67 69
68 Notice that a trigger has a set of operations 70 Notice that a trigger has a set of operations attached:
69 71
70 * :file:`set_trigger_state`, switch the trigge 72 * :file:`set_trigger_state`, switch the trigger on/off on demand.
71 * :file:`validate_device`, function to validat 73 * :file:`validate_device`, function to validate the device when the current
72 trigger gets changed. 74 trigger gets changed.
73 75
74 More details 76 More details
75 ============ 77 ============
76 .. kernel-doc:: include/linux/iio/trigger.h 78 .. kernel-doc:: include/linux/iio/trigger.h
77 .. kernel-doc:: drivers/iio/industrialio-trigg 79 .. kernel-doc:: drivers/iio/industrialio-trigger.c
78 :export: 80 :export:
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.