Lines Matching +full:stm32 +full:- +full:timer +full:- +full:trigger
3 Contact: linux-iio@vger.kernel.org
11 Contact: linux-iio@vger.kernel.org
17 periodic timer, GPIO or high resolution timer).
19 Contains trigger type specific elements. These do not
21 X is the IIO index of the trigger.
25 Contact: linux-iio@vger.kernel.org
31 Contact: linux-iio@vger.kernel.org
38 Contact: linux-iio@vger.kernel.org
44 The contents of the label are free-form, but there are some
51 * "proximity-wifi"
52 * "proximity-lte"
53 * "proximity-wifi-lte"
54 * "proximity-wifi-left"
55 * "proximity-wifi-right"
60 The "-left" and "-right" labels are for devices with multiple
66 * "proximity-palmrest" indicates proximity to the keyboard's palmrest
67 * "proximity-palmrest-left" indicates proximity to the left part of the palmrest
68 * "proximity-palmrest-right" indicates proximity to the right part of the palmrest
69 * "proximity-lap" indicates the device is being used on someone's lap
71 Note "proximity-lap" is special in that its value may be
75 For accelerometers used in 2-in-1s with 360° (yoga-style) hinges,
79 * "accel-base"
80 * "accel-display"
85 * "accel-camera"
89 Contact: linux-iio@vger.kernel.org
99 Contact: linux-iio@vger.kernel.org
110 The stm32-timer-trigger has the additional characteristic that
119 Contact: linux-iio@vger.kernel.org
124 - a small discrete set of values like "0 2 4 6 8"
125 - a range with minimum, step and maximum frequencies like
130 Contact: linux-iio@vger.kernel.org
137 Contact: linux-iio@vger.kernel.org
146 Contact: linux-iio@vger.kernel.org
156 channels refer to the same signal. The 'i' channel contains the in-phase
160 What: /sys/bus/iio/devices/iio:deviceX/in_voltageY-voltageZ_raw
162 Contact: linux-iio@vger.kernel.org
165 channel Y - channel Z where these channel numbers apply to the
174 Contact: linux-iio@vger.kernel.org
185 Contact: linux-iio@vger.kernel.org
194 Contact: linux-iio@vger.kernel.org
199 What: /sys/.../iio:deviceX/in_capacitanceY-capacitanceZ_raw
201 Contact: linux-iio@vger.kernel.org
204 channel Y - channel Z where these channel numbers apply to the
210 What: /sys/.../iio:deviceX/in_capacitanceY-capacitanceZ_zeropoint
212 Contact: linux-iio@vger.kernel.org
236 Contact: linux-iio@vger.kernel.org
242 between ambient (reference) and distant temperature for contact-
248 Contact: linux-iio@vger.kernel.org
256 Contact: linux-iio@vger.kernel.org
267 Contact: linux-iio@vger.kernel.org
276 Contact: linux-iio@vger.kernel.org
285 Contact: linux-iio@vger.kernel.org
293 Contact: linux-iio@vger.kernel.org
306 Contact: linux-iio@vger.kernel.org
317 Contact: linux-iio@vger.kernel.org
327 Contact: linux-iio@vger.kernel.org
337 Contact: linux-iio@vger.kernel.org
345 Contact: linux-iio@vger.kernel.org
353 Contact: linux-iio@vger.kernel.org
361 Contact: linux-iio@vger.kernel.org
367 Contact: linux-iio@vger.kernel.org
374 Contact: linux-iio@vger.kernel.org
380 Contact: linux-iio@vger.kernel.org
412 Contact: linux-iio@vger.kernel.org
435 What: /sys/bus/iio/devices/iio:deviceX/in_voltage-voltage_scale
470 Contact: linux-iio@vger.kernel.org
491 Contact: linux-iio@vger.kernel.org
502 Contact: linux-iio@vger.kernel.org
506 - a small discrete set of values like "0 2 4 6 8"
507 - a range specified as "[min step max]"
529 Contact: linux-iio@vger.kernel.org
540 Contact: linux-iio@vger.kernel.org
551 Contact: linux-iio@vger.kernel.org
560 Contact: linux-iio@vger.kernel.org
568 Contact: linux-iio@vger.kernel.org
580 What: /sys/.../iio:deviceX/in_voltage-voltage_scale_available
587 Contact: linux-iio@vger.kernel.org
599 Contact: linux-iio@vger.kernel.org
606 Contact: linux-iio@vger.kernel.org
615 Contact: linux-iio@vger.kernel.org
625 Contact: linux-iio@vger.kernel.org
634 Contact: linux-iio@vger.kernel.org
646 Contact: linux-iio@vger.kernel.org
658 Contact: linux-iio@vger.kernel.org
681 Contact: linux-iio@vger.kernel.org
691 Contact: linux-iio@vger.kernel.org
701 Contact: linux-iio@vger.kernel.org
728 Contact: linux-iio@vger.kernel.org
749 Contact: linux-iio@vger.kernel.org
752 to user-space.
790 Contact: linux-iio@vger.kernel.org
844 Contact: linux-iio@vger.kernel.org
869 Contact: linux-iio@vger.kernel.org
881 Contact: linux-iio@vger.kernel.org
887 signal is allowed to remain out-of-range before a reset
937 Contact: linux-iio@vger.kernel.org
963 Contact: linux-iio@vger.kernel.org
966 to device specific units used to set the event trigger
1021 Contact: linux-iio@vger.kernel.org
1071 Contact: linux-iio@vger.kernel.org
1161 Contact: linux-iio@vger.kernel.org
1171 Contact: linux-iio@vger.kernel.org
1181 Contact: linux-iio@vger.kernel.org
1196 Contact: linux-iio@vger.kernel.org
1210 Contact: linux-iio@vger.kernel.org
1236 Contact: linux-iio@vger.kernel.org
1247 Contact: linux-iio@vger.kernel.org
1260 Contact: linux-iio@vger.kernel.org
1273 Contact: linux-iio@vger.kernel.org
1281 Contact: linux-iio@vger.kernel.org
1290 Contact: linux-iio@vger.kernel.org
1298 What: /sys/bus/iio/devices/iio:deviceX/trigger/current_trigger
1300 Contact: linux-iio@vger.kernel.org
1302 The name of the trigger source being used, as per string given
1307 Contact: linux-iio@vger.kernel.org
1313 Contact: linux-iio@vger.kernel.org
1315 Actually start the buffer capture up. Will start trigger
1324 Contact: linux-iio@vger.kernel.org
1348 What: /sys/.../iio:deviceX/bufferY/in_voltageY-voltageZ_en
1360 Contact: linux-iio@vger.kernel.org
1381 Contact: linux-iio@vger.kernel.org
1384 and hence the form in which it is read from user-space.
1405 Contact: linux-iio@vger.kernel.org
1437 Contact: linux-iio@vger.kernel.org
1441 what is enabled and may not be contiguous. Thus for user-space
1452 Contact: linux-iio@vger.kernel.org
1459 Contact: linux-iio@vger.kernel.org
1466 Contact: linux-iio@vger.kernel.org
1477 Contact: linux-iio@vger.kernel.org
1486 Contact: linux-iio@vger.kernel.org
1494 Contact: linux-iio@vger.kernel.org
1497 on-chip EEPROM. After power-up or chip reset the device will
1504 Contact: linux-iio@vger.kernel.org
1523 Contact: linux-iio@vger.kernel.org
1534 Contact: linux-iio@vger.kernel.org
1536 Unit-less light intensity. Modifiers both and ir indicate
1545 Contact: linux-iio@vger.kernel.org
1559 Contact: linux-iio@vger.kernel.org
1567 Contact: linux-iio@vger.kernel.org
1573 Contact: linux-iio@vger.kernel.org
1585 Contact: linux-iio@vger.kernel.org
1594 Contact: linux-iio@vger.kernel.org
1602 channels refer to the same signal. The 'i' channel contains the in-phase
1611 Contact: linux-iio@vger.kernel.org
1620 Contact: linux-iio@vger.kernel.org
1628 Contact: linux-iio@vger.kernel.org
1636 Contact: linux-iio@vger.kernel.org
1644 Contact: linux-iio@vger.kernel.org
1651 Contact: linux-iio@vger.kernel.org
1661 Non-blocking read will retrieve the available samples from the
1669 Contact: linux-iio@vger.kernel.org
1671 A read-only value indicating the bytes of data available in the
1679 Contact: linux-iio@vger.kernel.org
1681 A read-only boolean value that indicates if the hardware fifo is
1686 device settings allows it (e.g. if a trigger is set that samples
1697 trigger to use buffer mode since the watermark settings
1703 Contact: linux-iio@vger.kernel.org
1714 Contact: linux-iio@vger.kernel.org
1716 Read-only entry that contains a single integer specifying the
1722 buffers are limited to 32-64 samples, some hardware buffers
1728 Contact: linux-iio@vger.kernel.org
1739 Contact: linux-iio@vger.kernel.org
1750 Contact: linux-iio@vger.kernel.org
1767 Contact: linux-iio@vger.kernel.org
1777 Contact: linux-iio@vger.kernel.org
1798 Contact: linux-iio@vger.kernel.org
1808 Contact: linux-iio@vger.kernel.org
1815 Contact: linux-iio@vger.kernel.org
1826 Contact: linux-iio@vger.kernel.org
1829 base-10 logarithm of hydrodium ions in a litre of water.
1837 Contact: linux-iio@vger.kernel.org
1848 way (platform data and / or device-tree), the main hardware
1858 [0, 1, 0; 1, 0, 0; 0, 0, -1]. Identity matrix
1874 An implementor might consider that for a hand-held device, a
1888 front-view camera;
1895 Contact: linux-iio@vger.kernel.org
1902 Contact: linux-iio@vger.kernel.org
1912 Contact: linux-iio@vger.kernel.org
1923 Contact: linux-iio@vger.kernel.org
1929 - "up" : counter device is increasing.
1930 - "down": counter device is decreasing.
1934 Contact: linux-iio@vger.kernel.org
1943 Contact: linux-iio@vger.kernel.org
1952 Contact: linux-iio@vger.kernel.org
1966 Contact: linux-iio@vger.kernel.org
1975 Contact: linux-iio@vger.kernel.org
1982 Contact: linux-iio@vger.kernel.org
1989 Contact: linux-iio@vger.kernel.org
1996 Contact: linux-iio@vger.kernel.org
2005 Contact: linux-iio@vger.kernel.org
2012 Contact: linux-iio@vger.kernel.org
2023 Contact: linux-iio@vger.kernel.org
2032 Contact: linux-iio@vger.kernel.org
2036 contaminant build-up in a measurement chamber or optical
2047 Contact: linux-iio@vger.kernel.org
2064 Contact: linux-iio@vger.kernel.org
2068 - a range specified as "[min step max]"
2074 Contact: linux-iio@vger.kernel.org
2084 Contact: linux-iio@vger.kernel.org
2091 Contact: linux-iio@vger.kernel.org
2096 Units and the exact meaning of value are device-specific.
2100 Contact: linux-iio@vger.kernel.org
2108 Contact: linux-iio@vger.kernel.org
2113 single-tap's or two double-tap's.
2117 Contact: linux-iio@vger.kernel.org
2123 Contact: linux-iio@vger.kernel.org
2130 Contact: linux-iio@vger.kernel.org
2137 Contact: linux-iio@vger.kernel.org
2145 Contact: linux-iio@vger.kernel.org
2154 Contact: linux-iio@vger.kernel.org
2161 Contact: linux-iio@vger.kernel.org
2163 An example format is 16-bytes, 2-digits-per-byte, HEX-string