| Michael Hennerich | f9a7e9b | 2011-02-07 11:05:46 +0100 | [diff] [blame] | 1 | What: /sys/bus/iio/devices/triggerX/trigger_now |
| 2 | KernelVersion: 2.6.38 |
| 3 | Contact: linux-iio@vger.kernel.org |
| 4 | Description: |
| 5 | This file is provided by the iio-trig-sysfs stand-alone trigger |
| 6 | driver. Writing this file with any value triggers an event |
| 7 | driven driver, associated with this trigger, to capture data |
| 8 | into an in kernel buffer. This approach can be valuable during |
| 9 | automated testing or in situations, where other trigger methods |
| 10 | are not applicable. For example no RTC or spare GPIOs. |
| 11 | X is the IIO index of the trigger. |
| Cristina Opriceana | 655665d | 2015-08-06 14:17:53 +0300 | [diff] [blame] | 12 | |
| 13 | What: /sys/bus/iio/devices/triggerX/name |
| 14 | KernelVersion: 2.6.39 |
| 15 | Contact: linux-iio@vger.kernel.org |
| 16 | Description: |
| 17 | The name attribute holds a description string for the current |
| 18 | trigger. In order to associate the trigger with an IIO device |
| 19 | one should write this name string to |
| 20 | /sys/bus/iio/devices/iio:deviceY/trigger/current_trigger. |
| Cristina Opriceana | e0950d3 | 2015-08-12 14:28:34 +0300 | [diff] [blame^] | 21 | |
| 22 | What: /sys/bus/iio/devices/iio_sysfs_trigger/add_trigger |
| 23 | KernelVersion: 2.6.39 |
| 24 | Contact: linux-iio@vger.kernel.org |
| 25 | Description: |
| 26 | This attribute is provided by the iio-trig-sysfs stand-alone |
| 27 | driver and it is used to activate the creation of a new trigger. |
| 28 | In order to achieve this, one should write a positive integer |
| 29 | into the associated file, which will serve as the id of the |
| 30 | trigger. If the trigger with the specified id is already present |
| 31 | in the system, an invalid argument message will be returned. |