0001 What: /sys/bus/iio/devices/triggerX/trigger_now
0002 KernelVersion: 2.6.38
0003 Contact: linux-iio@vger.kernel.org
0004 Description:
0005 This file is provided by the iio-trig-sysfs stand-alone trigger
0006 driver. Writing this file with any value triggers an event
0007 driven driver, associated with this trigger, to capture data
0008 into an in kernel buffer. This approach can be valuable during
0009 automated testing or in situations, where other trigger methods
0010 are not applicable. For example no RTC or spare GPIOs.
0011 X is the IIO index of the trigger.
0012
0013 What: /sys/bus/iio/devices/triggerX/name
0014 KernelVersion: 2.6.39
0015 Contact: linux-iio@vger.kernel.org
0016 Description:
0017 The name attribute holds a description string for the current
0018 trigger. In order to associate the trigger with an IIO device
0019 one should write this name string to
0020 /sys/bus/iio/devices/iio:deviceY/trigger/current_trigger.
0021
0022 What: /sys/bus/iio/devices/iio_sysfs_trigger/add_trigger
0023 KernelVersion: 2.6.39
0024 Contact: linux-iio@vger.kernel.org
0025 Description:
0026 This attribute is provided by the iio-trig-sysfs stand-alone
0027 driver and it is used to activate the creation of a new trigger.
0028 In order to achieve this, one should write a positive integer
0029 into the associated file, which will serve as the id of the
0030 trigger. If the trigger with the specified id is already present
0031 in the system, an invalid argument message will be returned.
0032
0033 What: /sys/bus/iio/devices/iio_sysfs_trigger/remove_trigger
0034 KernelVersion: 2.6.39
0035 Contact: linux-iio@vger.kernel.org
0036 Description:
0037 This attribute is used to unregister and delete a previously
0038 created trigger from the list of available triggers. In order to
0039 achieve this, one should write a positive integer into the
0040 associated file, representing the id of the trigger that needs
0041 to be removed. If the trigger can't be found, an invalid
0042 argument message will be returned to the user.
