Home
last modified time | relevance | path

Searched refs:signals (Results 1 – 25 of 367) sorted by relevance

12345678910>>...15

/linux/arch/arm/mach-spear/
A Dpl080.c28 } signals[16] = {{0, 0}, }; variable
38 if (signals[signal].busy && in pl080_get_signal()
39 (signals[signal].val != cd->muxval)) { in pl080_get_signal()
45 if (!signals[signal].busy) { in pl080_get_signal()
58 signals[signal].busy++; in pl080_get_signal()
59 signals[signal].val = cd->muxval; in pl080_get_signal()
72 if (!signals[signal].busy) in pl080_put_signal()
75 signals[signal].busy--; in pl080_put_signal()
/linux/tools/testing/selftests/arm64/fp/
A DREADME30 Terminated by signal 15, no error, iterations=9467, signals=1014
33 Terminated by signal 15, no error, iterations=9448, signals=1028
36 Terminated by signal 15, no error, iterations=9436, signals=1039
39 Terminated by signal 15, no error, iterations=9421, signals=1039
42 Terminated by signal 15, no error, iterations=9403, signals=1039
45 Terminated by signal 15, no error, iterations=9385, signals=1036
48 Terminated by signal 15, no error, iterations=9376, signals=1039
51 Terminated by signal 15, no error, iterations=9361, signals=1039
54 Terminated by signal 15, no error, iterations=9350, signals=1039
/linux/drivers/reset/
A Dreset-imx7.c25 const struct imx7_src_signal *signals; member
33 const struct imx7_src_signal *signals; member
51 const struct imx7_src_signal *signal = &imx7src->signals[id]; in imx7_reset_update()
95 const unsigned int bit = imx7src->signals[id].bit; in imx7_reset_set()
129 .signals = imx7_src_signals,
223 const unsigned int bit = imx7src->signals[id].bit; in imx8mq_reset_set()
265 .signals = imx8mq_src_signals,
318 const unsigned int bit = imx7src->signals[id].bit; in imx8mp_reset_set()
352 .signals = imx8mp_src_signals,
371 imx7src->signals = variant->signals; in imx7_reset_probe()
A DKconfig92 Say Y to control the reset signals provided by reset controller.
102 Say Y if you want to control reset signals provided by this
161 reset signals provided by AOSS for Modem, Venus, ADSP,
170 to control reset signals provided by PDC for Modem, Compute,
200 firmware controlling all the reset signals.
259 Say Y if you want to control reset signals provided by System Control
269 on UniPhier SoCs. Say Y if you want to control reset signals
/linux/drivers/gpu/drm/i915/gt/
A Dintel_breadcrumbs.c94 if (!list_empty(&ce->signals)) in remove_signaling_context()
110 if (!list_is_last(&rq->signal_link, &ce->signals) && in check_signal_order()
115 if (!list_is_first(&rq->signal_link, &ce->signals) && in check_signal_order()
208 list_for_each_entry_rcu(rq, &ce->signals, signal_link) { in signal_irq_work()
362 if (list_empty(&ce->signals)) { in insert_breadcrumb()
365 pos = &ce->signals; in insert_breadcrumb()
381 list_for_each_prev(pos, &ce->signals) { in insert_breadcrumb()
462 if (list_empty(&ce->signals)) in intel_context_remove_breadcrumbs()
465 list_for_each_entry_safe(rq, rn, &ce->signals, signal_link) { in intel_context_remove_breadcrumbs()
495 list_for_each_entry_rcu(rq, &ce->signals, signal_link) in print_signals()
/linux/drivers/counter/
A Dinterrupt-cnt.c23 struct counter_signal signals; member
182 priv->signals.name = devm_kasprintf(dev, GFP_KERNEL, "IRQ %d", in interrupt_cnt_probe()
184 if (!priv->signals.name) in interrupt_cnt_probe()
187 priv->counter.signals = &priv->signals; in interrupt_cnt_probe()
192 priv->synapses.signal = &priv->signals; in interrupt_cnt_probe()
/linux/Documentation/trace/coresight/
A Dcoresight-ect.rst14 individual input and output hardware signals known as triggers to and from
50 The hardware trigger signals can also be connected to non-CoreSight devices
72 capable of generating or using trigger signals.::
100 Individual trigger connection information. This describes trigger signals for
108 * ``in_types`` : functional types for in signals.
109 * ``out_signals`` : output trigger signals for this connection.
110 * ``out_types`` : functional types for out signals.
127 If a connection has zero signals in either the 'in' or 'out' triggers then
177 * ``chan_free``: Show channels with no attached signals.
185 dangerous output signals to be set.
[all …]
/linux/Documentation/driver-api/
A Dhsi.rst15 The serial protocol uses two signals, DATA and FLAG as combined data and clock
16 signals and an additional READY signal for flow control. An additional WAKE
17 signal can be used to wakeup the chips from standby modes. The signals are
18 commonly prefixed by AC for signals going from the application die to the
19 cellular die and CA for signals going the other way around.
A Dptp.rst25 - Period output signals configurable from user space
83 - 3 Periodic signals (optional interrupt)
91 - GPIO outputs can produce periodic signals
103 - Programmable output periodic signals
/linux/tools/lib/subcmd/
A Dsigchain.c13 static struct sigchain_signal signals[SIGCHAIN_MAX_SIGNALS]; variable
23 struct sigchain_signal *s = signals + sig; in sigchain_push()
36 struct sigchain_signal *s = signals + sig; in sigchain_pop()
/linux/drivers/tty/
A Dsynclink_gt.c729 info->signals |= SerialSignal_DTR; in set_termios()
731 info->signals |= SerialSignal_RTS; in set_termios()
1199 if (info->signals & SerialSignal_RI) in line_info()
1308 info->signals |= SerialSignal_RTS; in unthrottle()
1919 info->signals |= SerialSignal_DSR; in dsr_change()
1939 info->signals |= SerialSignal_CTS; in cts_change()
1974 info->signals |= SerialSignal_DCD; in dcd_change()
2011 info->signals |= SerialSignal_RI; in ri_change()
2014 info->signals &= ~SerialSignal_RI; in ri_change()
2671 s = info->signals; in wait_mgsl_event()
[all …]
/linux/Documentation/devicetree/bindings/gpio/
A Dgpio-eic-sprd.txt11 connections. A debounce mechanism is used to capture the input signals'
19 The EIC-latch sub-module is used to latch some special power down signals
21 clock to capture signals.
23 The EIC-async sub-module uses a 32kHz clock to capture the short signals
28 when detecting input signals.
A Dnvidia,tegra186-gpio.txt10 read/write the value of, numerous GPIO signals. Routing of GPIO signals to
24 b) GPIO registers, which allow manipulation of the GPIO signals. In some GPIO
48 Each GPIO controller can generate a number of interrupt signals. Each signal
50 number of interrupt signals generated by a controller varies as a rough function
54 Each GPIO controller in fact generates multiple interrupts signals for each set
56 interrupt signals generated by a set-of-ports. The intent is for each generated
59 per-port-set signals is reported via a separate register. Thus, a driver needs
/linux/Documentation/devicetree/bindings/reset/
A Dreset.txt3 This binding is intended to represent the hardware reset signals present
4 internally in most IC (SoC, FPGA, ...) designs. Reset signals for whole
24 may be reset. Instead, reset signals should be represented in the DT node
27 block node for dedicated reset signals. The intent of this binding is to give
28 appropriate software access to the reset signals in order to manage the HW,
/linux/Documentation/devicetree/bindings/arm/
A Dcoresight-cti.yaml20 output hardware trigger signals. CTIs can have a maximum number of input and
21 output hardware trigger signals (8 each for v1 CTI, 32 each for v2 CTI). The
31 In general the connections between CTI and components via the trigger signals
41 binding can be declared with no explicit trigger signals. This will result
58 signals to GEN_IO.
60 Note that some hardware trigger signals can be connected to non-CoreSight
132 A trigger connections child node which describes the trigger signals
155 signals. Types in this array match to the corresponding signal in the
172 signals. Types in this array match to the corresponding signal
181 List of CTI trigger out signals that will be blocked from becoming
/linux/Documentation/devicetree/bindings/display/panel/
A Dpanel-common.yaml96 # and timing of those control signals are device-specific and left for panel
98 # used for panels that implement compatible control signals.
107 signals (or active high power down signals) can be supported by inverting
118 while active. Active high reset signals can be supported by inverting the
125 The tearing effect signal is active high. Active low signals can be
143 # backlight control through GPIO, PWM or other signals connected to an external
/linux/drivers/pinctrl/aspeed/
A Dpinctrl-aspeed.c265 char *signals = get_defined_signals(pdesc); in aspeed_pinmux_set_mux() local
268 pfunc->name, pdesc->name, pin, signals, in aspeed_pinmux_set_mux()
270 kfree(signals); in aspeed_pinmux_set_mux()
408 char *signals = get_defined_signals(pdesc); in aspeed_gpio_request_enable() local
411 pdesc->name, offset, signals); in aspeed_gpio_request_enable()
412 kfree(signals); in aspeed_gpio_request_enable()
/linux/Documentation/devicetree/bindings/usb/
A Dbrcm,usb-pinmap.yaml22 description: Interrupt for signals mirrored to out-gpios.
27 description: Array of one or two GPIO pins used for input signals.
39 description: Array of one GPIO pin used for output signals.
/linux/Documentation/devicetree/bindings/media/i2c/
A Dtvp5150.txt4 (and also SECAM in the TVP5151 case) video signals to either 8-bit 4:2:2 YUV
55 - sdtv-standards: Set the possible signals to which the hardware tries to lock
67 sdtv-standards = <SDTV_STD_PAL_M>; /* limit to pal-m signals */
79 sdtv-standards = <SDTV_STD_NTSC_M>; /* limit to ntsc-m signals */
/linux/Documentation/devicetree/bindings/leds/
A Dleds-bcm6328.txt16 is usually 1:1 for hardware to LED signals, but through the activity/link
60 signal sources. Up to four link hardware signals can get muxed into
61 these LEDs. Only valid for LEDs 0 to 7, where LED signals 0 to 3 may
62 be muxed to LEDs 0 to 3, and signals 4 to 7 may be muxed to LEDs
66 signal sources. Up to four activity hardware signals can get muxed into
67 these LEDs. Only valid for LEDs 0 to 7, where LED signals 0 to 3 may
68 be muxed to LEDs 0 to 3, and signals 4 to 7 may be muxed to LEDs
/linux/arch/mips/kernel/
A Dentry.S86 # signals dont change between
130 # signals dont change between
139 work_notifysig: # deal with pending signals and
/linux/Documentation/ABI/testing/
A Dsysfs-bus-coresight-devices-cti35 Description: (Read) Input trigger signals from connected device <N>
41 Description: (Read) Functional types for the input trigger signals
48 Description: (Read) Output trigger signals to connected device <N>
54 Description: (Read) Functional types for the output trigger signals
129 Description: (Read) read current status of input trigger signals
135 Description: (Read) read current status of output trigger signals.
214 Description: (Read) show channels with no attached trigger signals.
/linux/drivers/usb/serial/
A Dupd78f0730.c187 int signals; in upd78f0730_tiocmget() local
193 signals = private->line_signals; in upd78f0730_tiocmget()
196 res = ((signals & UPD78F0730_DTR) ? TIOCM_DTR : 0) | in upd78f0730_tiocmget()
197 ((signals & UPD78F0730_RTS) ? TIOCM_RTS : 0); in upd78f0730_tiocmget()
/linux/Documentation/devicetree/bindings/media/
A Dst-rc.txt11 protocol used for receiving remote control signals. rx-mode should
14 protocol used for transmitting remote control signals. tx-mode should
/linux/arch/m68k/
A DKconfig.debug45 bool "Disable BDM signals"
48 Disable the ColdFire CPU's BDM signals.

Completed in 47 milliseconds

12345678910>>...15