Lines Matching +full:compound +full:- +full:device
3 Contact: linux-iio@vger.kernel.org
5 Hardware chip or device accessed by one communication port.
7 index of the device.
11 Contact: linux-iio@vger.kernel.org
14 May be provided by a device driver that also has an IIO device
25 Contact: linux-iio@vger.kernel.org
27 Directory of attributes relating to the buffer for the device.
31 Contact: linux-iio@vger.kernel.org
33 Description of the physical chip / device for device X.
38 Contact: linux-iio@vger.kernel.org
40 Optional symbolic label for a device.
42 individual device.
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
64 instead indicate proximity to a specific part of the device:
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
92 buffered samples and events for device X.
99 Contact: linux-iio@vger.kernel.org
108 then it is to be found in the base device directory.
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
222 within the measurement range of the device. The naming is
236 Contact: linux-iio@vger.kernel.org
240 sensor is associated with one part of a compound device (e.g.
242 between ambient (reference) and distant temperature for contact-
249 Contact: linux-iio@vger.kernel.org
257 Contact: linux-iio@vger.kernel.org
260 but should match other such assignments on device).
268 Contact: linux-iio@vger.kernel.org
277 Contact: linux-iio@vger.kernel.org
280 but should match other such assignments on device).
287 Contact: linux-iio@vger.kernel.org
291 assignments on device).
293 desired period of time, the application should sum-up the delta
301 Contact: linux-iio@vger.kernel.org
305 assignments on device).
307 desired period of time, the application should sum-up the delta
315 Contact: linux-iio@vger.kernel.org
323 Contact: linux-iio@vger.kernel.org
327 device).
336 Contact: linux-iio@vger.kernel.org
347 Contact: linux-iio@vger.kernel.org
357 Contact: linux-iio@vger.kernel.org
369 Contact: linux-iio@vger.kernel.org
378 Contact: linux-iio@vger.kernel.org
386 Contact: linux-iio@vger.kernel.org
394 Contact: linux-iio@vger.kernel.org
402 Contact: linux-iio@vger.kernel.org
408 Contact: linux-iio@vger.kernel.org
415 Contact: linux-iio@vger.kernel.org
421 Contact: linux-iio@vger.kernel.org
424 used for averaging is device specific. The converting rules for
453 Contact: linux-iio@vger.kernel.org
455 If known for a device, offset to be added to <type>[Y]_raw prior
462 device. Note that this is different to calibbias which
476 What: /sys/bus/iio/devices/iio:deviceX/in_voltage-voltage_scale
513 Contact: linux-iio@vger.kernel.org
515 If known for a device, scale to be applied to <type>Y[_name]_raw
548 Contact: linux-iio@vger.kernel.org
552 icm42600: For this device values are real physical offsets
563 Contact: linux-iio@vger.kernel.org
567 - a small discrete set of values like "0 2 4 6 8"
568 - a range specified as "[min step max]"
599 Contact: linux-iio@vger.kernel.org
610 Contact: linux-iio@vger.kernel.org
614 - a small discrete set of values like "1 8 16"
615 - a range specified as "[min step max]"
624 Contact: linux-iio@vger.kernel.org
635 Contact: linux-iio@vger.kernel.org
644 Contact: linux-iio@vger.kernel.org
652 Contact: linux-iio@vger.kernel.org
664 What: /sys/.../iio:deviceX/in_voltage-voltage_scale_available
671 Contact: linux-iio@vger.kernel.org
685 Contact: linux-iio@vger.kernel.org
692 Contact: linux-iio@vger.kernel.org
701 Contact: linux-iio@vger.kernel.org
711 Contact: linux-iio@vger.kernel.org
720 Contact: linux-iio@vger.kernel.org
726 a continuous frequency generating device, such as
732 Contact: linux-iio@vger.kernel.org
744 Contact: linux-iio@vger.kernel.org
768 Contact: linux-iio@vger.kernel.org
778 Contact: linux-iio@vger.kernel.org
788 Contact: linux-iio@vger.kernel.org
815 Contact: linux-iio@vger.kernel.org
819 (out_altvoltageZ) of the device X. The number must always be
836 Contact: linux-iio@vger.kernel.org
839 to user-space.
877 Contact: linux-iio@vger.kernel.org
881 then either the device will report an event which ever direction
886 different values, but the device can only enable both thresholds
931 Contact: linux-iio@vger.kernel.org
936 device will report an event which ever direction a single
941 different values, but the device can only enable both rate of
956 Contact: linux-iio@vger.kernel.org
968 Contact: linux-iio@vger.kernel.org
974 signal is allowed to remain out-of-range before a reset
1024 Contact: linux-iio@vger.kernel.org
1026 Specifies the value of threshold that the device is comparing
1035 value is in raw device units or in processed units (as _raw
1050 Contact: linux-iio@vger.kernel.org
1053 to device specific units used to set the event trigger
1108 Contact: linux-iio@vger.kernel.org
1110 Specifies the hysteresis of threshold that the device is comparing
1158 Contact: linux-iio@vger.kernel.org
1161 device is comparing against for the events enabled by
1168 value is in raw device units or in processed units (as _raw
1248 Contact: linux-iio@vger.kernel.org
1258 Contact: linux-iio@vger.kernel.org
1268 Contact: linux-iio@vger.kernel.org
1283 Contact: linux-iio@vger.kernel.org
1297 Contact: linux-iio@vger.kernel.org
1323 Contact: linux-iio@vger.kernel.org
1334 Contact: linux-iio@vger.kernel.org
1347 Contact: linux-iio@vger.kernel.org
1360 Contact: linux-iio@vger.kernel.org
1368 Contact: linux-iio@vger.kernel.org
1377 Contact: linux-iio@vger.kernel.org
1380 device is comparing against for the events enabled by
1387 Contact: linux-iio@vger.kernel.org
1394 Contact: linux-iio@vger.kernel.org
1400 Contact: linux-iio@vger.kernel.org
1403 if first device and appropriate.
1411 Contact: linux-iio@vger.kernel.org
1441 What: /sys/.../iio:deviceX/bufferY/in_voltageY-voltageZ_en
1453 Contact: linux-iio@vger.kernel.org
1476 Contact: linux-iio@vger.kernel.org
1479 and hence the form in which it is read from user-space.
1500 Contact: linux-iio@vger.kernel.org
1538 Contact: linux-iio@vger.kernel.org
1542 what is enabled and may not be contiguous. Thus for user-space
1553 Contact: linux-iio@vger.kernel.org
1560 Contact: linux-iio@vger.kernel.org
1563 present in the device at a given time.
1567 Contact: linux-iio@vger.kernel.org
1578 Contact: linux-iio@vger.kernel.org
1581 device (e.g.: human activity sensors report energy burnt by the
1587 Contact: linux-iio@vger.kernel.org
1595 Contact: linux-iio@vger.kernel.org
1597 Writing '1' stores the current device configuration into
1598 on-chip EEPROM. After power-up or chip reset the device will
1605 Contact: linux-iio@vger.kernel.org
1624 Contact: linux-iio@vger.kernel.org
1637 Contact: linux-iio@vger.kernel.org
1639 Unit-less light intensity. Modifiers both and ir indicate
1649 Contact: linux-iio@vger.kernel.org
1663 Contact: linux-iio@vger.kernel.org
1671 Contact: linux-iio@vger.kernel.org
1677 Contact: linux-iio@vger.kernel.org
1689 Contact: linux-iio@vger.kernel.org
1698 Contact: linux-iio@vger.kernel.org
1706 channels refer to the same signal. The 'i' channel contains the in-phase
1715 Contact: linux-iio@vger.kernel.org
1717 Activates a device feature that runs in firmware/hardware.
1724 Contact: linux-iio@vger.kernel.org
1732 Contact: linux-iio@vger.kernel.org
1740 Contact: linux-iio@vger.kernel.org
1748 Contact: linux-iio@vger.kernel.org
1755 Contact: linux-iio@vger.kernel.org
1765 Non-blocking read will retrieve the available samples from the
1773 Contact: linux-iio@vger.kernel.org
1775 A read-only value indicating the bytes of data available in the
1783 Contact: linux-iio@vger.kernel.org
1785 A read-only boolean value that indicates if the hardware fifo is
1786 currently enabled or disabled. If the device does not have a
1790 device settings allows it (e.g. if a trigger is set that samples
1795 fifo reaches the hardware fifo watermark level the device will
1796 flush its hardware fifo to the device buffer. Doing a non
1797 blocking read on the device when no samples are present in the
1798 device buffer will also force a flush.
1802 guarantees that the hardware fifo is flushed to the device
1805 What: /sys/bus/iio/devices/iio:device*/buffer/hwfifo_timeout
1807 Contact: linux-iio@vger.kernel.org
1818 Contact: linux-iio@vger.kernel.org
1820 Read-only entry that contains a single integer specifying the
1821 current watermark level for the hardware fifo. If the device
1826 buffers are limited to 32-64 samples, some hardware buffers
1832 Contact: linux-iio@vger.kernel.org
1835 for the hardware fifo of this device. If the device does not
1843 Contact: linux-iio@vger.kernel.org
1846 for the hardware fifo of this device. If the device does not
1854 Contact: linux-iio@vger.kernel.org
1871 Contact: linux-iio@vger.kernel.org
1881 Contact: linux-iio@vger.kernel.org
1902 Contact: linux-iio@vger.kernel.org
1912 Contact: linux-iio@vger.kernel.org
1919 Contact: linux-iio@vger.kernel.org
1925 to heatup the device and get rid of any condensation
1930 Contact: linux-iio@vger.kernel.org
1933 base-10 logarithm of hydrodium ions in a litre of water.
1941 Contact: linux-iio@vger.kernel.org
1952 way (platform data and / or device-tree), the main hardware
1962 [0, 1, 0; 1, 0, 0; 0, 0, -1]. Identity matrix
1978 An implementor might consider that for a hand-held device, a
1992 front-view camera;
1999 Contact: linux-iio@vger.kernel.org
2007 Contact: linux-iio@vger.kernel.org
2011 Raw counter device counts from channel Y. For quadrature
2017 Contact: linux-iio@vger.kernel.org
2021 Raw counter device index value from channel Y. This attribute
2028 Contact: linux-iio@vger.kernel.org
2034 - "up" : counter device is increasing.
2035 - "down": counter device is decreasing.
2039 Contact: linux-iio@vger.kernel.org
2043 Raw counter device counters direction for channel Y.
2048 Contact: linux-iio@vger.kernel.org
2050 Optional symbolic label to a device channel.
2057 Contact: linux-iio@vger.kernel.org
2071 Contact: linux-iio@vger.kernel.org
2080 Contact: linux-iio@vger.kernel.org
2087 Contact: linux-iio@vger.kernel.org
2094 Contact: linux-iio@vger.kernel.org
2101 Contact: linux-iio@vger.kernel.org
2110 Contact: linux-iio@vger.kernel.org
2117 Contact: linux-iio@vger.kernel.org
2128 Contact: linux-iio@vger.kernel.org
2137 Contact: linux-iio@vger.kernel.org
2141 contaminant build-up in a measurement chamber or optical
2152 Contact: linux-iio@vger.kernel.org
2156 reference device.
2169 Contact: linux-iio@vger.kernel.org
2173 - a range specified as "[min step max]"
2179 Contact: linux-iio@vger.kernel.org
2189 Contact: linux-iio@vger.kernel.org
2191 Device generates an event on a single or double tap.
2196 Contact: linux-iio@vger.kernel.org
2198 Specifies the threshold value that the device is comparing
2201 Units and the exact meaning of value are device-specific.
2205 Contact: linux-iio@vger.kernel.org
2213 Contact: linux-iio@vger.kernel.org
2218 single-tap's or two double-tap's.
2222 Contact: linux-iio@vger.kernel.org
2228 Contact: linux-iio@vger.kernel.org
2235 Contact: linux-iio@vger.kernel.org
2242 Contact: linux-iio@vger.kernel.org
2250 Contact: linux-iio@vger.kernel.org
2259 Contact: linux-iio@vger.kernel.org
2266 Contact: linux-iio@vger.kernel.org
2268 An example format is 16-bytes, 2-digits-per-byte, HEX-string
2273 Contact: linux-iio@vger.kernel.org
2282 Contact: linux-iio@vger.kernel.org
2289 Contact: linux-iio@vger.kernel.org
2297 Contact: linux-iio@vger.kernel.org
2310 Contact: linux-iio@vger.kernel.org
2312 Optional symbolic label to a device channel event.
2319 Contact: linux-iio@vger.kernel.org
2325 Contact: linux-iio@vger.kernel.org
2331 Contact: linux-iio@vger.kernel.org
2339 Contact: linux-iio@vger.kernel.org
2345 Contact: linux-iio@vger.kernel.org