Home
last modified time | relevance | path

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

12345678910>>...42

/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-6.6/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"
14 compatible = "ti,am335x-pocketbeagle", "ti,am335x-bone", "ti,am33xx";
17 stdout-path = &uart0;
21 pinctrl-names = "default";
22 pinctrl-0 = <&usr_leds_pins>;
24 compatible = "gpio-leds";
26 led-usr0 {
[all …]
Dam335x-regor.dtsi1 // SPDX-License-Identifier: GPL-2.0
9 model = "Phytec AM335x phyBOARD-REGOR";
10 compatible = "phytec,am335x-regor", "phytec,am335x-phycore-som", "ti,am33xx";
13 compatible = "regulator-fixed";
14 regulator-name = "vcc3v3";
15 regulator-min-microvolt = <3300000>;
16 regulator-max-microvolt = <3300000>;
17 regulator-boot-on;
21 user_leds: user-leds {
22 compatible = "gpio-leds";
[all …]
/kernel/linux/linux-5.10/arch/arm/boot/dts/
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-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-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-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-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"
14 compatible = "ti,am335x-pocketbeagle", "ti,am335x-bone", "ti,am33xx";
17 stdout-path = &uart0;
21 pinctrl-names = "default";
22 pinctrl-0 = <&usr_leds_pins>;
24 compatible = "gpio-leds";
29 linux,default-trigger = "heartbeat";
[all …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-5.10/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, than the trigger turns the LED on and than 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 …]
/kernel/linux/linux-6.6/drivers/scsi/mpt3sas/
Dmpt3sas_trigger_diag.h7 * Copyright (C) 2012-2014 LSI Corporation
8 * Copyright (C) 2013-2014 Avago Technologies
9 * (mailto: MPT-FusionLinux.pdl@avagotech.com)
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 …]
/kernel/linux/linux-5.10/drivers/scsi/mpt3sas/
Dmpt3sas_trigger_diag.h7 * Copyright (C) 2012-2014 LSI Corporation
8 * Copyright (C) 2013-2014 Avago Technologies
9 * (mailto: MPT-FusionLinux.pdl@avagotech.com)
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 …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/leds/
Dregister-bit-led.txt4 where single bits in a certain register can turn on/off a
5 single LED. The register bit LEDs appear as children to the
10 Each LED is represented as a sub-node of the syscon device. Each
13 LED sub-node properties:
16 - compatible : must be "register-bit-led"
17 - offset : register offset to the register controlling this LED
18 - mask : bit mask for the bit controlling this LED in the register
22 - label : (optional)
24 - linux,default-trigger : (optional)
26 - default-state: (optional) The initial state of the LED
[all …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-5.10/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 …]
/kernel/linux/linux-6.6/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 …]
/kernel/linux/linux-6.6/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 <swarren@nvidia.com>
13 - if:
17 const: nvidia,tegra210-timer
21 # Either a single combined interrupt or up to 14 individual interrupts
27 - if:
31 - items:
[all …]

12345678910>>...42