change system file

hc

2024-10-09 244b2c5ca8b14627e4a17755e5922221e121c771

 kernel/Documentation/driver-api/iio/triggers.rst
..
..
@@ -2,11 +2,9 @@
2
2
 Triggers
3
3
 ========
4
4
 
5
-* struct :c:type:`iio_trigger` — industrial I/O trigger device
5
+* struct iio_trigger — industrial I/O trigger device
6
6
 * :c:func:`devm_iio_trigger_alloc` — Resource-managed iio_trigger_alloc
7
-* :c:func:`devm_iio_trigger_free` — Resource-managed iio_trigger_free
8
7
 * :c:func:`devm_iio_trigger_register` — Resource-managed iio_trigger_register
9
-* :c:func:`devm_iio_trigger_unregister` — Resource-managed
10
8
   iio_trigger_unregister
11
9
 * :c:func:`iio_trigger_validate_own_device` — Check if a trigger and IIO
12
10
   device belong to the same device
..
..
@@ -38,7 +36,7 @@
38
36
 
39
37
 * :file:`/sys/bus/iio/devices/iio:device{X}/trigger/*`, this directory is
40
38
   created once the device supports a triggered buffer. We can associate a
41
-  trigger with our  device by writing the trigger's name in the
39
+  trigger with our device by writing the trigger's name in the
42
40
   :file:`current_trigger` file.
43
41
 
44
42
 IIO trigger setup
..
..
@@ -65,7 +63,7 @@
65
63
 IIO trigger ops
66
64
 ===============
67
65
 
68
-* struct :c:type:`iio_trigger_ops` — operations structure for an iio_trigger.
66
+* struct iio_trigger_ops — operations structure for an iio_trigger.
69
67
 
70
68
 Notice that a trigger has a set of operations attached:
71
69