Home
last modified time | relevance | path

Searched +full:single +full:- +full:trigger (Results 1 – 25 of 1007) sorted by relevance

12345678910>>...41

/linux-6.14.4/Documentation/ABI/testing/
Dsysfs-bus-coresight-devices-cti1 What: /sys/bus/coresight/devices/<cti-name>/enable
7 What: /sys/bus/coresight/devices/<cti-name>/powered
13 What: /sys/bus/coresight/devices/<cti-name>/ctmid
19 What: /sys/bus/coresight/devices/<cti-name>/nr_trigger_cons
25 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/name
31 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_signals
35 Description: (Read) Input trigger signals from connected device <N>
37 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_types
41 Description: (Read) Functional types for the input trigger signals
44 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/out_signals
[all …]
Dsysfs-class-led-trigger-usbport4 Contact: linux-[email protected]
5 linux-[email protected]
7 Every dir entry represents a single USB port that can be
8 selected for the USB port trigger. Selecting ports makes trigger
/linux-6.14.4/arch/arm/boot/dts/ti/omap/
Domap5-uevm.dts1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (C) 2013 Texas Instruments Incorporated - https://www.ti.com/
5 /dts-v1/;
7 #include "omap5-board-common.dtsi"
11 compatible = "ti,omap5-uevm", "ti,omap5";
18 reserved-memory {
19 #address-cells = <2>;
20 #size-cells = <2>;
23 dsp_memory_region: dsp-memory@95000000 {
24 compatible = "shared-dma-pool";
[all …]
Dam335x-osd3358-sm-red.dts1 //SPDX-License-Identifier: GPL-2.0
2 /* Copyright (C) 2018 Octavo Systems LLC - https://www.octavosystems.com/
9 /dts-v1/;
12 #include "am335x-osd335x-common.dtsi"
13 #include <dt-bindings/interrupt-controller/irq.h>
15 #include <dt-bindings/display/tda998x.h>
18 model = "Octavo Systems OSD3358-SM-RED";
19 compatible = "oct,osd3358-sm-refdesign", "ti,am335x-bone-black", "ti,am335x-bone", "ti,am33xx";
23 regulator-min-microvolt = <1800000>;
24 regulator-max-microvolt = <1800000>;
[all …]
Dam335x-bone-common.dtsi1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (C) 2012 Texas Instruments Incorporated - https://www.ti.com/
9 cpu0-supply = <&dcdc2_reg>;
19 stdout-path = &uart0;
23 pinctrl-names = "default";
24 pinctrl-0 = <&user_leds_s0>;
26 compatible = "gpio-leds";
31 linux,default-trigger = "heartbeat";
32 default-state = "off";
38 linux,default-trigger = "mmc0";
[all …]
Dam335x-boneblue.dts1 // SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (C) 2012 Texas Instruments Incorporated - https://www.ti.com/
5 /dts-v1/;
8 #include "am335x-osd335x-common.dtsi"
9 #include <dt-bindings/interrupt-controller/irq.h>
13 compatible = "ti,am335x-bone-blue", "ti,am33xx";
16 stdout-path = &uart0;
20 pinctrl-names = "default";
21 pinctrl-0 = <&user_leds_s0>;
23 compatible = "gpio-leds";
[all …]
Dam335x-pocketbeagle.dts1 // SPDX-License-Identifier: GPL-2.0
3 * Copyright (C) 2012 Texas Instruments Incorporated - https://www.ti.com/
7 /dts-v1/;
10 #include "am335x-osd335x-common.dtsi"
11 #include <dt-bindings/leds/common.h>
15 compatible = "ti,am335x-pocketbeagle", "ti,am335x-bone", "ti,am33xx";
18 stdout-path = &uart0;
22 pinctrl-names = "default";
23 pinctrl-0 = <&usr_leds_pins>;
25 compatible = "gpio-leds";
[all …]
Dam335x-regor.dtsi1 // SPDX-License-Identifier: GPL-2.0
8 #include <dt-bindings/gpio/gpio.h>
9 #include <dt-bindings/pinctrl/am33xx.h>
12 model = "Phytec AM335x phyBOARD-REGOR";
13 compatible = "phytec,am335x-regor", "phytec,am335x-phycore-som", "ti,am33xx";
16 compatible = "regulator-fixed";
17 regulator-name = "vcc3v3";
18 regulator-min-microvolt = <3300000>;
19 regulator-max-microvolt = <3300000>;
20 regulator-boot-on;
[all …]
Domap3-overo-base.dtsi1 // SPDX-License-Identifier: GPL-2.0-only
17 led-controller {
18 compatible = "pwm-leds";
20 led-1 {
23 max-brightness = <127>;
24 linux,default-trigger = "mmc0";
29 compatible = "ti,omap-twl4030";
37 compatible = "regulator-fixed";
38 regulator-name = "hsusb2_vbus";
39 regulator-min-microvolt = <5000000>;
[all …]
Dlogicpd-som-lv-baseboard.dtsi1 // SPDX-License-Identifier: GPL-2.0-only
5 compatible = "gpio-keys";
6 pinctrl-names = "default";
7 pinctrl-0 = <&gpio_key_pins>;
13 wakeup-source;
18 compatible = "ti,omap-twl4030";
24 compatible = "gpio-leds";
25 pinctrl-names = "default";
26 pinctrl-0 = <&led_pins &led_pins_wkup>;
31 linux,default-trigger = "cpu0";
[all …]
/linux-6.14.4/Documentation/leds/
Dledtrig-usbport.rst2 USB port LED trigger
5 This LED trigger can be used for signalling to the user a presence of USB device
13 Please note that this trigger allows selecting multiple USB ports for a single
18 1) Device with single USB LED and few physical ports
28 port may be handled by ohci-platform, ehci-platform and xhci-hcd. If there is
32 This trigger can be activated from user space on led class devices as shown
35 echo usbport > trigger
38 Documentation/ABI/testing/sysfs-class-led-trigger-usbport
40 Example use-case::
42 echo usbport > trigger
[all …]
Dledtrig-oneshot.rst2 One-shot LED Trigger
5 This is a LED trigger useful for signaling the user of an event where there are
6 no clear trap points to put standard led-on and led-off settings. Using this
7 trigger, the application needs only to signal the trigger when an event has
8 happened, then the trigger turns the LED on and then keeps it off for a
11 This trigger is meant to be usable both for sporadic and dense events. In the
12 first case, the trigger produces a clear single controlled blink for each
16 A one-shot LED only stays in a constant state when there are no events. An
20 The trigger can be activated from user space on led class devices as shown
23 echo oneshot > trigger
[all …]
/linux-6.14.4/drivers/scsi/mpt3sas/
Dmpt3sas_trigger_diag.h7 * Copyright (C) 2012-2014 LSI Corporation
8 * Copyright (C) 2013-2014 Avago Technologies
9 * (mailto: MPT-[email protected])
24 * LIMITATION, ANY WARRANTIES OR CONDITIONS OF TITLE, NON-INFRINGEMENT,
43 * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301,
46 /* Diagnostic Trigger Configuration Data Structures */
54 /* trigger types */
60 /* trigger names */
66 /* master trigger bitmask */
72 /* fake firmware event for trigger */
[all …]
/linux-6.14.4/Documentation/gpu/amdgpu/
Dprocess-isolation.rst1 .. SPDX-License-Identifier: GPL-2.0
7 … that support partitionable graphics engines, this feature can be enabled on a per-partition basis.
9 …the GPU is complete. This may be preferable in some use cases, such as a single-user system where …
17 ------------------
19 … sysfs. On GPUs that do not support graphics engine partitioning, only a single partition will be …
23 .. code-block:: console
31 For devices with a single partition or those that do not support partitions, there will be only one…
33 .. code-block:: console
42 …trigger a cleaner shader to clean up the LDS and GPR state on the graphics engine. When process is…
44 To manually trigger the execution of the cleaner shader, write `0` to the `run_cleaner_shader` sysf…
[all …]
/linux-6.14.4/tools/tracing/rtla/src/
Dtrace.c1 // SPDX-License-Identifier: GPL-2.0
14 * enable_tracer_by_name - enable a tracer on the given instance
31 return -1; in enable_tracer_by_name()
38 * disable_tracer - set nop tracer to the insta
51 * create_instance - create a trace instance with *instance_name
59 * destroy_instance - remove a trace instance and free the data
68 * save_trace_to_file - save the trace output of the instance to the file
76 int retval = -1; in save_trace_to_file()
81 return -1; in save_trace_to_file()
109 * collect_registered_events - call the existing callback function for the event
[all …]
/linux-6.14.4/Documentation/trace/coresight/
Dcoresight-ect.rst1 .. SPDX-License-Identifier: GPL-2.0
4 CoreSight Embedded Cross Trigger (CTI & CTM).
11 --------------------
13 The CoreSight Cross Trigger Interface (CTI) is a hardware device that takes
15 devices and interconnects them via the Cross Trigger Matrix (CTM) to other
21 0 C 0----------->: : +======>(other CTI channel IO)
22 0 P 0<-----------: : v
24 0000000 : CTI :<=========>*CTM*<====>: CTI :---+
25 ####### in_trigs : : (id 0-3) ***** ::::::: v
26 # ETM #----------->: : ^ #######
[all …]
/linux-6.14.4/Documentation/devicetree/bindings/timer/
Dnvidia,tegra-timer.yaml1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/timer/nvidia,tegra-timer.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Stephen Warren <[email protected]>
13 - if:
17 const: nvidia,tegra210-timer
21 # Either a single combined interrupt or up to 14 individual interrupts
27 - if:
31 - items:
[all …]
/linux-6.14.4/Documentation/admin-guide/media/
Dmgb4.rst1 .. SPDX-License-Identifier: GPL-2.0
7 ---------------
13 There are two types of parameters - global / PCI card related, found under
23 | 0 - No module present
24 | 1 - FPDL3
25 | 2 - GMSL
33 | 1 - FPDL3
34 | 2 - GMSL
42 PRODUCT-REVISION-SERIES-SERIAL
55 | 0 - single
[all …]
/linux-6.14.4/drivers/iio/
Dindustrialio-trigger.c1 // SPDX-License-Identifier: GPL-2.0-only
2 /* The industrial I/O core, trigger handling functions
17 #include <linux/iio/iio-opaque.h>
18 #include <linux/iio/trigger.h>
23 /* RFC - Question of approach
24 * Make the common case (single sensor single trigger)
25 * simple by starting trigger capture from when first sensors
29 * of the trigger. (not implemented)
36 /* Single list of all available triggers */
41 * name_show() - retrieve useful identifying name
[all …]
/linux-6.14.4/Documentation/driver-api/
Dreset.rst1 .. SPDX-License-Identifier: GPL-2.0-only
13 the `consumer driver interface <#consumer-driver-interface>`__ (`API reference
14 <#reset-consumer-api>`__), which allows peripheral drivers to request control
16 <#reset-controller-driver-interface>`__ (`API reference
17 <#reset-controller-driver-api>`__), which is used by drivers for reset
25 --------
37 Most commonly this is a single bit in reset controller register space that
39 is self-clearing and can be used to trigger a predetermined pulse on the
41 In more complicated reset controls, a single trigger action can launch a
61 trigger reset pulses, or to query reset line status.
[all …]
/linux-6.14.4/tools/perf/pmu-events/arch/arm64/
Dcommon-and-microarch.json129 "PublicDescription": "Attributable Level 1 data cache write-back",
132 "BriefDescription": "Attributable Level 1 data cache write-back"
147 "PublicDescription": "Attributable Level 2 data cache write-back",
150 "BriefDescription": "Attributable Level 2 data cache write-back"
273 "PublicDescription": "Access to another socket in a multi-socket system",
276 "BriefDescription": "Access to another socket in a multi-socket system"
303 … "PublicDescription": "Attributable memory read access to another socket in a multi-socket system",
306 … "BriefDescription": "Attributable memory read access to another socket in a multi-socket system"
309 …"PublicDescription": "Level 1 data cache long-latency read miss. The counter counts each memory r…
312 "BriefDescription": "Level 1 data cache long-latency read miss"
[all …]
/linux-6.14.4/arch/mips/boot/dts/mobileye/
Deyeq6h-pins.dtsi1 // SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
9 * [0] | MUX_SEL | 0 - GPIO, 1 - alternative func
14 * [13:12] | PUD | pull-up/pull-down. 0, 3 - no, 1 - PD, 2 - PU
16 * [15] | ST_CFG | Hysteretic input enable (Schmitt trigger)
20 // TODO: use pinctrl-single,bias-pullup
21 // TODO: use pinctrl-single,bias-pulldown
22 // TODO: use pinctrl-single,drive-strength
23 // TODO: use pinctrl-single,input-schmitt
25 i2c0_pins: i2c0-pins {
26 pinctrl-single,pins = <
[all …]
/linux-6.14.4/arch/arm/kernel/
Dhw_breakpoint.c1 // SPDX-License-Identifier: GPL-2.0-only
10 * HW_breakpoint: a unified kernel/user-space hardware breakpoint facility,
13 #define pr_fmt(fmt) "hw-breakpoint: " fmt
151 /* We don't support the memory-mapped interface. */ in debug_arch_supported()
199 * a single watchpoint register for the time being. This way, we always in get_num_wrps()
216 return core_has_mismatch_brps() ? brps - 1 : brps; in get_num_brps()
257 return -ENODEV; in enable_monitor_mode()
265 return -EPERM; in enable_monitor_mode()
293 * Check if 8-bit byte-address select is available.
333 addr = info->address; in arch_install_hw_breakpoint()
[all …]
/linux-6.14.4/tools/tracing/rtla/tests/
Dhwnoise.t2 # SPDX-License-Identifier: GPL-2.0
9 "hwnoise --help"
11 "hwnoise -c 0 -T 1 -d 5s -q"
13 "hwnoise -a 5 -d 30s"
15 "hwnoise -P F:1 -c 0 -r 900000 -d 1M -q"
16 check "stop the trace if a single sample is higher than 1 us" \
17 "hwnoise -s 1 -T 1 -t -d 30s"
18 check "enable a trace event trigger" \
19 …"hwnoise -t -e osnoise:irq_noise trigger=\"hist:key=desc,duration:sort=desc,duration:vals=hitcount…
/linux-6.14.4/drivers/comedi/drivers/
Damplc_pci230.c1 // SPDX-License-Identifier: GPL-2.0+
8 * COMEDI - Linux Control and Measurement Device Interface
35 * --------- ---------
43 * The AI subdevice has 16 single-ended channels or 8 differential
46 * The PCI230 and PCI260 cards have 12-bit resolution. The PCI230+ and
47 * PCI260+ cards have 16-bit resolution.
51 * or PCI260 then it actually uses a "pseudo-differential" mode where the
62 * 0 => [-10, +10] V
63 * 1 => [-5, +5] V
64 * 2 => [-2.5, +2.5] V
[all …]

12345678910>>...41