| /linux/arch/arm/boot/dts/ti/omap/ |
| H A D | omap5-uevm.dts | 1 // 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 …]
|
| H A D | am335x-osd3358-sm-red.dts | 1 //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 …]
|
| H A D | am335x-bone-common.dtsi | 1 // 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 …]
|
| H A D | am335x-boneblue.dts | 1 // 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 …]
|
| H A D | am335x-pocketbeagle.dts | 1 // 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 …]
|
| H A D | am335x-regor.dtsi | 1 // 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 …]
|
| H A D | logicpd-som-lv-baseboard.dtsi | 1 // 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/Documentation/leds/ |
| H A D | ledtrig-usbport.rst | 2 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 …]
|
| H A D | ledtrig-oneshot.rst | 2 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/drivers/scsi/mpt3sas/ |
| H A D | mpt3sas_trigger_diag.h | 7 * 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 …]
|
| /linux/tools/tracing/rtla/src/ |
| H A D | trace.c | 1 // 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() 84 return -1; in save_trace_to_file() 113 * collect_registered_events - call the existing callback function for the event [all …]
|
| /linux/Documentation/trace/coresight/ |
| H A D | coresight-ect.rst | 1 .. 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/Documentation/devicetree/bindings/timer/ |
| H A D | nvidia,tegra-timer.yaml | 1 # 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 …]
|
| /linux/drivers/iio/ |
| H A D | industrialio-trigger.c | 1 // 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/Documentation/driver-api/ |
| H A D | reset.rst | 1 .. 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/arch/arm/kernel/ |
| H A D | hw_breakpoint.c | 1 // 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/arch/mips/boot/dts/mobileye/ |
| H A D | eyeq6h-pins.dtsi | 1 // 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/drivers/comedi/drivers/ |
| H A D | amplc_pci230.c | 1 // 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 …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-led-trigger-usbport | 4 Contact: linux-leds@vger.kernel.org 5 linux-usb@vger.kernel.org 7 Every dir entry represents a single USB port that can be 8 selected for the USB port trigger. Selecting ports makes trigger
|
| /linux/tools/perf/pmu-events/arch/arm64/ |
| H A D | common-and-microarch.json | 129 "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" 283 "PublicDescription": "Access to another socket in a multi-socket system", 286 "BriefDescription": "Access to another socket in a multi-socket system" 323 … "PublicDescription": "Attributable memory read access to another socket in a multi-socket system", 326 … "BriefDescription": "Attributable memory read access to another socket in a multi-socket system" 329 …"PublicDescription": "Level 1 data cache long-latency read miss. The counter counts each memory r… 332 "BriefDescription": "Level 1 data cache long-latency read miss" [all …]
|
| /linux/Documentation/i2c/ |
| H A D | smbus-protocol.rst | 24 single data byte, the functions using SMBus protocol operation names execute 60 This sends a single bit to the device, at the place of the Rd/Wr bit:: 72 This reads a single byte from a device, without specifying a device 87 This operation is the reverse of Receive Byte: it sends a single byte 102 This reads a single byte from a device, from a designated register. 133 This writes a single byte to a device, to a designated register. The 207 SMBus Block Write - Block Read Process Call 210 SMBus Block Write - Block Read Process Call was introduced in 238 * I2C bus drivers trigger SMBus Host Notify by a call to 240 * I2C drivers for devices which can trigger SMBus Host Notify will have [all …]
|
| /linux/drivers/net/phy/ |
| H A D | dp83640_reg.h | 1 /* SPDX-License-Identifier: GPL-2.0 */ 15 #define PTP_TSTS 0x0017 /* PTP Trigger Status Register */ 20 #define PTP_TXTS 0x001c /* PTP Transmit Timestamp Register, in four 16-bit reads */ 21 #define PTP_RXTS 0x001d /* PTP Receive Timestamp Register, in six? 16-bit reads */ 26 #define PTP_TRIG 0x0014 /* PTP Trigger Configuration Register */ 57 #define TRIG_SEL_SHIFT (10) /* PTP Trigger Select */ 59 #define TRIG_DIS (1<<9) /* Disable PTP Trigger */ 60 #define TRIG_EN (1<<8) /* Enable PTP Trigger */ 61 #define TRIG_READ (1<<7) /* Read PTP Trigger */ 62 #define TRIG_LOAD (1<<6) /* Load PTP Trigger */ [all …]
|
| /linux/tools/tracing/rtla/tests/ |
| H A D | hwnoise.t | 2 # SPDX-License-Identifier: GPL-2.0 9 "hwnoise --help" 0 "summary of hardware-related noise" 11 "hwnoise -c 0 -T 1 -d 5s -q" 0 13 "hwnoise -a 5 -d 10s" 2 "osnoise hit stop tracing" 15 "hwnoise -P F:1 -c 0 -r 900000 -d 10s -q" 16 check "stop the trace if a single sample is higher than 1 us" \ 17 "hwnoise -s 1 -T 1 -t -d 10s" 2 "Saving trace to osnoise_trace.txt" 18 check "enable a trace event trigger" \ 19 …"hwnoise -t -e osnoise:irq_noise --trigger=\"hist:key=desc,duration:sort=desc,duration:vals=hitcou…
|
| /linux/arch/arm/boot/dts/ti/keystone/ |
| H A D | keystone-k2g-ice.dts | 1 // SPDX-License-Identifier: GPL-2.0 5 * Copyright (C) 2017 Texas Instruments Incorporated - https://www.ti.com/ 7 /dts-v1/; 9 #include "keystone-k2g.dtsi" 10 #include <dt-bindings/net/ti-dp83867.h> 13 compatible = "ti,k2g-ice", "ti,k2g", "ti,keystone"; 21 reserved-memory { 22 #address-cells = <2>; 23 #size-cells = <2>; 26 dsp_common_memory: dsp-common-memory@81f800000 { [all …]
|
| /linux/Documentation/devicetree/bindings/leds/ |
| H A D | regulator-led.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/leds/regulator-led.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Linus Walleij <linus.walleij@linaro.org> 13 Regulator LEDs are powered by a single regulator such that they can 20 - $ref: common.yaml# 27 const: regulator-led 29 vled-supply: 35 linux,default-trigger: true [all …]
|