Searched full:triggers (Results 1 – 25 of 135) sorted by relevance
123456
/Documentation/iio/ |
D | iio_configfs.rst | 10 triggers). 30 3. Software triggers 33 One of the IIO default configfs groups is the "triggers" group. It is 35 under /config/iio/triggers. 37 IIO software triggers implementation offers support for creating multiple 76 Each trigger type has its own directory under /config/iio/triggers. Loading 78 /config/iio/triggers/trig-sample. 84 3.1 Hrtimer triggers creation and destruction 88 users to create hrtimer triggers under /config/iio/triggers/hrtimer. 92 $ mkdir /config/iio/triggers/hrtimer/instance1 [all …]
|
/Documentation/ABI/testing/ |
D | configfs-iio | 10 What: /config/iio/triggers 14 Industrial IO software triggers directory. 16 What: /config/iio/triggers/hrtimers
|
D | sysfs-bus-coresight-devices-cti | 23 Description: (Read) Number of devices connected to triggers on this CTI 25 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/name 31 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_signals 37 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_types 44 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/out_signals 50 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/out_types 196 Description: (Read) List of output triggers filtered across all connections. 227 Description: (Read) Read to see input triggers connected to selected view 234 Description: (Read) Read to see output triggers connected to selected view
|
D | sysfs-platform-dell-laptop | 27 This file allows to control the input triggers that 30 Read the file to see the triggers available. The ones 45 Note that not all the available triggers can be configured.
|
D | sysfs-bus-iio-trigger-sysfs | 6 driver. Writing this file with any value triggers an event 38 created trigger from the list of available triggers. In order to
|
D | sysfs-class-led | 70 You can change triggers in a similar manner to the way an IO 81 gpio and backlight triggers. In case of the backlight trigger,
|
D | sysfs-driver-hid-corsair | 6 where G-keys triggers their regular key codes. "HW" for
|
D | sysfs-bus-iio-frequency-ad9523 | 27 Writing '1' triggers the clock distribution synchronization
|
/Documentation/trace/coresight/ |
D | coresight-ect.rst | 14 individual input and output hardware signals known as triggers to and from 30 The CTI driver enables the programming of the CTI to attach triggers to 34 activating connected output triggers there, unless filtered by the CTI 84 * ``nr_trigger_cons`` : total connections - triggers<N> directories. 88 * ``triggers<N>``: contains list of triggers for an individual connection. 97 triggers<N> directories 103 Each triggers directory has a set of parameters describing the triggers for 127 If a connection has zero signals in either the 'in' or 'out' triggers then 133 This provides an easy way to attach triggers to channels, without needing 180 * ``chan_xtrigs_in``: Read to show the input triggers attached to [all …]
|
/Documentation/driver-api/iio/ |
D | triggers.rst | 2 Triggers title 24 There are two locations in sysfs related to triggers: 29 Because triggers can be very different depending on type there are few 34 * :file:`sampling_frequency`, some timer based triggers use this attribute to
|
D | index.rst | 16 triggers
|
/Documentation/devicetree/bindings/dma/ |
D | st,stm32-mdma.yaml | 43 0x00: Each MDMA request triggers a buffer transfer (max 128 bytes) 44 0x1: Each MDMA request triggers a block transfer (max 64K bytes) 45 0x2: Each MDMA request triggers a repeated block transfer 46 0x3: Each MDMA request triggers a linked list transfer
|
/Documentation/input/ |
D | gamepad.rst | 20 / [__ TL __] [__ TR __] \ | Front Triggers 58 - Triggers 59 Triggers are located on the upper-side of the pad in vertical direction. 61 Left- and Right-Triggers, the lower buttons Z-Left and Z-Right. 157 - Triggers: 168 reported as "right" triggers (BTN_TR/ABS_HAT1X).
|
/Documentation/hwmon/ |
D | w83793.rst | 65 For voltage sensors, an alarm triggers if the measured value is below 67 For temperature sensors, an alarm triggers if the measured value goes 70 For fan sensors, an alarm triggers if the measured value is below the 101 If the case open alarm triggers, it will stay in this state unless cleared
|
D | pc87360.rst | 127 associated low, high and overtemperature limits, each of which triggers an 165 triggers an alarm when crossed. 177 If an alarm triggers, it will remain triggered until the hardware register 182 a once-only alarm triggers, it may take 2 seconds for it to show, and 2
|
/Documentation/devicetree/bindings/iio/adc/ |
D | at91_adc.txt | 23 - atmel,adc-use-external-triggers: Boolean to enable the external triggers 56 atmel,adc-use-external-triggers;
|
/Documentation/leds/ |
D | leds-class.rst | 12 is a kernel based source of led events. Triggers can either be simple or 15 nand-disk and sharpsl-charge triggers. With led triggers disabled, the code 18 Complex triggers while available to all LEDs have LED specific 27 You can change triggers in a similar manner to the way an IO scheduler 187 particular LED (ACPI?). The addition of triggers provided by the LED driver
|
D | leds-blinkm.rst | 18 a) LED class interface for use with triggers 38 assign triggers on each color.
|
D | uleds.rst | 6 triggers and can also be used to implement virtual LEDs.
|
D | ledtrig-transient.rst | 22 triggers. 25 triggers it supports and a default trigger. During registration, activation 37 being able to actually change the LED state. Once driver is resumed, triggers
|
/Documentation/driver-api/ |
D | ptp.rst | 81 - 2 Time stamp external triggers, programmable polarity (opt. interrupt) 90 - GPIO inputs can time stamp external triggers 104 - Programmable inputs can time stamp external triggers
|
/Documentation/devicetree/bindings/thermal/ |
D | brcm,avs-tmon.txt | 11 - interrupts: temperature monitor interrupt, for high/low threshold triggers,
|
/Documentation/x86/x86_64/ |
D | machinecheck.rst | 42 finds MCEs it triggers an exponential speedup (poll more often) on 44 triggers an exponential backoff (poll less often) on the polling
|
/Documentation/devicetree/bindings/arm/mstar/ |
D | mstar,l3bridge.yaml | 23 are and install a barrier that triggers the required pipeline flush.
|
/Documentation/trace/ |
D | events.rst | 328 6. Event triggers 335 with attached triggers is invoked, the set of trigger commands 342 Triggers are added to and removed from a particular event by writing 345 A given event can have any number of triggers associated with it, 349 Event triggers are implemented on top of "soft" mode, which means that 350 whenever a trace event has one or more triggers associated with it, 354 This scheme allows triggers to be invoked even for events that aren't 356 used for conditionally invoking triggers. 358 The syntax for event triggers is roughly based on the syntax for 366 can also enable triggers that are written into [all …]
|
123456