Home
last modified time | relevance | path

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

12345678910>>...23

/OK3568_Linux_fs/kernel/arch/arm/mach-spear/
H 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()
/OK3568_Linux_fs/kernel/tools/testing/selftests/arm64/fp/
H 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
/OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/gdb/gdb/
H A D0009-Fix-invalid-sigprocmask-call.patch24 * common/signals-state-save-restore.c (save_original_signals_state):
31 gdbsupport/signals-state-save-restore.cc | 2 +-
34 diff --git a/gdbsupport/signals-state-save-restore.cc b/gdbsupport/signals-state-save-restore.cc
36 --- a/gdbsupport/signals-state-save-restore.cc
37 +++ b/gdbsupport/signals-state-save-restore.cc
/OK3568_Linux_fs/kernel/drivers/reset/
H 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()
353 .signals = imx8mp_src_signals,
372 imx7src->signals = variant->signals; in imx7_reset_probe()
/OK3568_Linux_fs/u-boot/drivers/reset/
H A DKconfig10 controller drivers allow control over these reset signals. In some
22 controller drivers allow control over these reset signals. In some
40 Say Y if you want to control reset signals provided by system config
47 Enable support for manipulating Tegra's on-SoC reset signals via
54 Enable support for manipulating Tegra's on-SoC reset signals via IPC
69 Say Y if you want to control reset signals provided by System Control
80 is that some reset signals, like I2C or MISC reset multiple devices.
88 is that some reset signals, like I2C or MISC reset multiple devices.
95 is that some reset signals, like I2C or MISC reset multiple devices.
H A Dsandbox-reset.c20 struct sandbox_reset_signal signals[SANDBOX_RESET_SIGNALS]; member
46 sbr->signals[reset_ctl->id].asserted = true; in sandbox_reset_assert()
57 sbr->signals[reset_ctl->id].asserted = false; in sandbox_reset_deassert()
107 return sbr->signals[id].asserted; in sandbox_reset_query()
/OK3568_Linux_fs/kernel/Documentation/trace/coresight/
H 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 …]
/OK3568_Linux_fs/kernel/drivers/gpu/drm/i915/gt/
H A Dintel_breadcrumbs.c127 if (!list_empty(&ce->signals)) in remove_signaling_context()
143 if (!list_is_last(&rq->signal_link, &ce->signals) && in check_signal_order()
148 if (!list_is_first(&rq->signal_link, &ce->signals) && in check_signal_order()
252 list_for_each_entry_rcu(rq, &ce->signals, signal_link) { in signal_irq_work()
384 if (list_empty(&ce->signals)) { in insert_breadcrumb()
387 pos = &ce->signals; in insert_breadcrumb()
403 list_for_each_prev(pos, &ce->signals) { in insert_breadcrumb()
478 list_for_each_entry_rcu(rq, &ce->signals, signal_link) in print_signals()
/OK3568_Linux_fs/kernel/Documentation/driver-api/
H 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.
/OK3568_Linux_fs/kernel/tools/lib/subcmd/
H 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()
/OK3568_Linux_fs/kernel/drivers/tty/
H A Dsynclink_gt.c287 unsigned char signals; /* serial signal states */ member
722 info->signals &= ~(SerialSignal_RTS | SerialSignal_DTR); in set_termios()
730 info->signals |= SerialSignal_DTR; in set_termios()
732 info->signals |= SerialSignal_RTS; in set_termios()
1190 if (info->signals & SerialSignal_RTS) in line_info()
1192 if (info->signals & SerialSignal_CTS) in line_info()
1194 if (info->signals & SerialSignal_DTR) in line_info()
1196 if (info->signals & SerialSignal_DSR) in line_info()
1198 if (info->signals & SerialSignal_DCD) in line_info()
1200 if (info->signals & SerialSignal_RI) in line_info()
[all …]
/OK3568_Linux_fs/buildroot/package/lirc-tools/
H A DConfig.in10 signals of the most common IR remote controls. It contains a
11 daemon that decodes and sends IR signals, a mouse daemon
12 that translates IR signals to mouse movements and a couple
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/gpio/
H 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.
H 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
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/reset/
H 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,
/OK3568_Linux_fs/u-boot/doc/device-tree-bindings/reset/
H 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,
/OK3568_Linux_fs/u-boot/doc/device-tree-bindings/gpio/
H 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
/OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/
H A Dyuv-formats.rst9 YUV is the format native to TV broadcast and composite video signals. It
12 *color difference* signals, this way the green component can be
17 was added to transmit the color difference signals. Secondary in the YUV
/OK3568_Linux_fs/kernel/drivers/pinctrl/aspeed/
H A Dpinctrl-aspeed.c264 char *signals = get_defined_signals(pdesc); in aspeed_pinmux_set_mux() local
267 pfunc->name, pdesc->name, pin, signals, in aspeed_pinmux_set_mux()
269 kfree(signals); in aspeed_pinmux_set_mux()
407 char *signals = get_defined_signals(pdesc); in aspeed_gpio_request_enable() local
410 pdesc->name, offset, signals); in aspeed_gpio_request_enable()
411 kfree(signals); in aspeed_gpio_request_enable()
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/media/i2c/
H 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 */
/OK3568_Linux_fs/app/forlinx/flapp/src/plugins/allwinner/browser/
H A Dbookmarks.h52 signals:
193 signals:
253 signals:
279 signals:
/OK3568_Linux_fs/buildroot/package/libsigc/
H A DConfig.in7 C++. It allows you to define signals and to connect those
8 signals to any callback function, either global or a member
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/leds/
H 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
/OK3568_Linux_fs/yocto/meta-openembedded/meta-perl/recipes-perl/libipc/
H A Dlibipc-signal-perl_1.00.bb1 SUMMARY = "IPC::Signal - Utility functions dealing with signals"
3 dealing with signals."
/OK3568_Linux_fs/yocto/meta-openembedded/meta-xfce/recipes-extended/imsettings/imsettings/
H A Dimsettings-gcc10.patch15 -guint signals[LAST_SIGNAL];
16 +static guint signals[LAST_SIGNAL];

12345678910>>...23