1What: /sys/bus/iio/devices/triggerX/trigger_now 2KernelVersion: 2.6.38 3Contact: linux-iio@vger.kernel.org 4Description: 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. 12 13What: /sys/bus/iio/devices/triggerX/name 14KernelVersion: 2.6.39 15Contact: linux-iio@vger.kernel.org 16Description: 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. 21 22What: /sys/bus/iio/devices/iio_sysfs_trigger/add_trigger 23KernelVersion: 2.6.39 24Contact: linux-iio@vger.kernel.org 25Description: 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. 32 33What: /sys/bus/iio/devices/iio_sysfs_trigger/remove_trigger 34KernelVersion: 2.6.39 35Contact: linux-iio@vger.kernel.org 36Description: 37 This attribute is used to unregister and delete a previously 38 created trigger from the list of available triggers. In order to 39 achieve this, one should write a positive integer into the 40 associated file, representing the id of the trigger that needs 41 to be removed. If the trigger can't be found, an invalid 42 argument message will be returned to the user. 43