Home
last modified time | relevance | path

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

12345678910>>...17

/linux-6.6.21/arch/arm/mach-spear/
Dpl080.c26 } signals[16] = {{0, 0}, }; variable
36 if (signals[signal].busy && in pl080_get_signal()
37 (signals[signal].val != cd->muxval)) { in pl080_get_signal()
43 if (!signals[signal].busy) { in pl080_get_signal()
56 signals[signal].busy++; in pl080_get_signal()
57 signals[signal].val = cd->muxval; in pl080_get_signal()
70 if (!signals[signal].busy) in pl080_put_signal()
73 signals[signal].busy--; in pl080_put_signal()
/linux-6.6.21/tools/testing/selftests/arm64/fp/
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-6.6.21/drivers/reset/
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()
353 .signals = imx8mp_src_signals,
372 imx7src->signals = variant->signals; in imx7_reset_probe()
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
173 reset signals provided by AOSS for Modem, Venus, ADSP,
182 to control reset signals provided by PDC for Modem, Compute,
212 firmware controlling all the reset signals.
288 It provides reset signals for Armada 7040 and 385 SoC-s, Alleycat 3X
302 Say Y if you want to control reset signals provided by System Control
312 on UniPhier SoCs. Say Y if you want to control reset signals
/linux-6.6.21/drivers/gpu/drm/i915/gt/
Dintel_breadcrumbs.c95 if (!list_empty(&ce->signals)) in remove_signaling_context()
111 if (!list_is_last(&rq->signal_link, &ce->signals) && in check_signal_order()
116 if (!list_is_first(&rq->signal_link, &ce->signals) && in check_signal_order()
209 list_for_each_entry_rcu(rq, &ce->signals, signal_link) { in signal_irq_work()
363 if (list_empty(&ce->signals)) { in insert_breadcrumb()
366 pos = &ce->signals; in insert_breadcrumb()
382 list_for_each_prev(pos, &ce->signals) { in insert_breadcrumb()
464 if (list_empty(&ce->signals)) in intel_context_remove_breadcrumbs()
467 list_for_each_entry_safe(rq, rn, &ce->signals, signal_link) { in intel_context_remove_breadcrumbs()
497 list_for_each_entry_rcu(rq, &ce->signals, signal_link) in print_signals()
/linux-6.6.21/drivers/counter/
Dinterrupt-cnt.c22 struct counter_signal signals; member
197 priv->signals.name = devm_kasprintf(dev, GFP_KERNEL, "IRQ %d", in interrupt_cnt_probe()
199 if (!priv->signals.name) in interrupt_cnt_probe()
202 counter->signals = &priv->signals; in interrupt_cnt_probe()
207 priv->synapses.signal = &priv->signals; in interrupt_cnt_probe()
/linux-6.6.21/tools/lib/subcmd/
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-6.6.21/Documentation/trace/coresight/
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-6.6.21/Documentation/driver-api/
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.
Dptp.rst25 - Period output signals configurable from user space
99 - 3 Periodic signals (optional interrupt)
107 - GPIO outputs can produce periodic signals
119 - Programmable output periodic signals
131 periodic signals.
134 periodic signals.
/linux-6.6.21/drivers/tty/
Dsynclink_gt.c283 unsigned char signals; /* serial signal states */ member
713 info->signals &= ~(SerialSignal_RTS | SerialSignal_DTR); in set_termios()
721 info->signals |= SerialSignal_DTR; in set_termios()
723 info->signals |= SerialSignal_RTS; in set_termios()
1181 if (info->signals & SerialSignal_RTS) in line_info()
1183 if (info->signals & SerialSignal_CTS) in line_info()
1185 if (info->signals & SerialSignal_DTR) in line_info()
1187 if (info->signals & SerialSignal_DSR) in line_info()
1189 if (info->signals & SerialSignal_DCD) in line_info()
1191 if (info->signals & SerialSignal_RI) in line_info()
[all …]
/linux-6.6.21/Documentation/devicetree/bindings/gpio/
Dsprd,gpio-eic.yaml24 connections. A debounce mechanism is used to capture the input signals'
32 The EIC-latch sub-module is used to latch some special power down signals
34 clock to capture signals.
36 The EIC-async sub-module uses a 32kHz clock to capture the short signals
41 when detecting input signals.
Dnvidia,tegra186-gpio.yaml21 and read/write the value of, numerous GPIO signals. Routing of GPIO signals
35 b) GPIO registers, which allow manipulation of the GPIO signals. In some
60 Each GPIO controller can generate a number of interrupt signals. Each
62 ports. Thus, the number of interrupt signals generated by a controller
67 Each GPIO controller in fact generates multiple interrupts signals for
69 one of the interrupt signals generated by a set-of-ports. The intent is
72 The status of each of these per-port-set signals is reported via a
/linux-6.6.21/Documentation/devicetree/bindings/reset/
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-6.6.21/Documentation/gpu/amdgpu/display/
Ddcn-overview.rst67 2. Global sync signals (green): It is a set of synchronization signals composed
70 4. Sideband signals: All other signals that do not fit the previous one.
72 These signals are essential and play an important role in DCN. Nevertheless,
197 These atomic register updates are driven by global sync signals in DCN. In
199 signals page flip and vblank events it is helpful to understand how global sync
202 Global sync consists of three signals, VSTARTUP, VUPDATE, and VREADY. These are
206 The global sync signals always happen during VBlank, are independent from the
210 or userspace clients as it signals the point at which hardware latches to
218 The below picture illustrates the global sync signals:
222 These signals affect core DCN behavior. Programming them incorrectly will lead
/linux-6.6.21/Documentation/devicetree/bindings/usb/
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-6.6.21/Documentation/devicetree/bindings/arm/
Darm,coresight-cti.yaml19 output hardware trigger signals. CTIs can have a maximum number of input and
20 output hardware trigger signals (8 each for v1 CTI, 32 each for v2 CTI). The
30 In general the connections between CTI and components via the trigger signals
40 binding can be declared with no explicit trigger signals. This will result
57 signals to GEN_IO.
59 Note that some hardware trigger signals can be connected to non-CoreSight
134 A trigger connections child node which describes the trigger signals
157 signals. Types in this array match to the corresponding signal in the
174 signals. Types in this array match to the corresponding signal
183 List of CTI trigger out signals that will be blocked from becoming
/linux-6.6.21/Documentation/devicetree/bindings/display/panel/
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-6.6.21/Documentation/devicetree/bindings/media/i2c/
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-6.6.21/arch/mips/kernel/
Dentry.S85 # signals dont change between
129 # signals dont change between
138 work_notifysig: # deal with pending signals and
/linux-6.6.21/drivers/pinctrl/aspeed/
Dpinctrl-aspeed.c266 char *signals = get_defined_signals(pdesc); in aspeed_pinmux_set_mux() local
269 pfunc->name, pdesc->name, pin, signals, in aspeed_pinmux_set_mux()
271 kfree(signals); in aspeed_pinmux_set_mux()
409 char *signals = get_defined_signals(pdesc); in aspeed_gpio_request_enable() local
412 pdesc->name, offset, signals); in aspeed_gpio_request_enable()
413 kfree(signals); in aspeed_gpio_request_enable()
/linux-6.6.21/Documentation/devicetree/bindings/leds/
Dleds-bcm6328.yaml27 is usually 1:1 for hardware to LED signals, but through the activity/link
95 signals can get muxed into these LEDs. Only valid for LEDs 0 to 7,
96 where LED signals 0 to 3 may be muxed to LEDs 0 to 3, and signals 4 to
106 hardware signals can get muxed into these LEDs. Only valid for LEDs 0
107 to 7, where LED signals 0 to 3 may be muxed to LEDs 0 to 3, and
108 signals 4 to 7 may be muxed to LEDs 4 to 7. A signal can be muxed to
/linux-6.6.21/Documentation/ABI/testing/
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-6.6.21/Documentation/devicetree/bindings/media/
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-6.6.21/drivers/usb/serial/
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()

12345678910>>...17