43 lines · plain
1What: /sys/bus/iio/devices/triggerX/trigger_now2KernelVersion: 2.6.383Contact: linux-iio@vger.kernel.org4Description:5 This file is provided by the iio-trig-sysfs stand-alone trigger6 driver. Writing this file with any value triggers an event7 driven driver, associated with this trigger, to capture data8 into an in kernel buffer. This approach can be valuable during9 automated testing or in situations, where other trigger methods10 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/name14KernelVersion: 2.6.3915Contact: linux-iio@vger.kernel.org16Description:17 The name attribute holds a description string for the current18 trigger. In order to associate the trigger with an IIO device19 one should write this name string to20 /sys/bus/iio/devices/iio:deviceY/trigger/current_trigger.21 22What: /sys/bus/iio/devices/iio_sysfs_trigger/add_trigger23KernelVersion: 2.6.3924Contact: linux-iio@vger.kernel.org25Description:26 This attribute is provided by the iio-trig-sysfs stand-alone27 driver and it is used to activate the creation of a new trigger.28 In order to achieve this, one should write a positive integer29 into the associated file, which will serve as the id of the30 trigger. If the trigger with the specified id is already present31 in the system, an invalid argument message will be returned.32 33What: /sys/bus/iio/devices/iio_sysfs_trigger/remove_trigger34KernelVersion: 2.6.3935Contact: linux-iio@vger.kernel.org36Description:37 This attribute is used to unregister and delete a previously38 created trigger from the list of available triggers. In order to39 achieve this, one should write a positive integer into the40 associated file, representing the id of the trigger that needs41 to be removed. If the trigger can't be found, an invalid42 argument message will be returned to the user.43