Home
last modified time | relevance | path

Searched full:signals (Results 1 – 25 of 1885) sorted by relevance

12345678910>>...76

/OK3568_Linux_fs/u-boot/include/
H A Dreset.h17 * or in response to some error condition. Reset signals are often controlled
20 * reset controllers set or clear reset signals.
23 * controller will often implement multiple separate reset signals, since the
27 * Reset consumers/clients are the HW modules affected by reset signals. This
65 * signals.
71 * the API to all the reset signals in the bulk struct.
86 * client device; each device is assumed to have n reset signals associated
88 * mapping of client device reset signal indices to provider reset signals may
94 * list of reset signals.
102 * reset_get_bulk - Get/request all reset signals of a device.
[all …]
/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.
/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/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/gdb/
H A DSignals.html17 <title>Debugging with GDB: Signals</title>
19 <meta name="description" content="Debugging with GDB: Signals">
20 <meta name="keywords" content="Debugging with GDB: Signals">
64 <a name="Signals"></a>
70 <a name="Signals-1"></a>
71 <h3 class="section">5.4 Signals</h3>
72 <a name="index-signals"></a>
75 operating system defines the possible kinds of signals, and gives each
83 <a name="index-fatal-signals"></a>
84 <p>Some signals, including <code>SIGALRM</code>, are a normal part of the
[all …]
H A DSignaling.html101 the signal handling tables (see <a href="Signals.html#Signals">Signals</a>). The <code>signal</cod…
116 You can control the handling of signals from <small>GDB</small> with the
117 <code>handle</code> command (see <a href="Signals.html#Signals">Signals</a>).
128 (see <a href="Signals.html#Signals">Signals</a>).
132 <p>See <a href="Signals.html#stepping-into-signal-handlers">stepping into signal handlers</a>, for …
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/gdb/
H A DSignals.html17 <title>Debugging with GDB: Signals</title>
19 <meta name="description" content="Debugging with GDB: Signals">
20 <meta name="keywords" content="Debugging with GDB: Signals">
64 <a name="Signals"></a>
70 <a name="Signals-1"></a>
71 <h3 class="section">5.4 Signals</h3>
72 <a name="index-signals"></a>
75 operating system defines the possible kinds of signals, and gives each
83 <a name="index-fatal-signals"></a>
84 <p>Some signals, including <code>SIGALRM</code>, are a normal part of the
[all …]
H A DSignaling.html101 the signal handling tables (see <a href="Signals.html#Signals">Signals</a>). The <code>signal</cod…
116 You can control the handling of signals from <small>GDB</small> with the
117 <code>handle</code> command (see <a href="Signals.html#Signals">Signals</a>).
128 (see <a href="Signals.html#Signals">Signals</a>).
132 <p>See <a href="Signals.html#stepping-into-signal-handlers">stepping into signal handlers</a>, for …
/OK3568_Linux_fs/kernel/Documentation/driver-api/
H A Dgeneric-counter.rst80 A counter is defined as a set of input signals associated with count
82 input signals as defined by the respective count functions. Within the
84 each associated with a set of Signals, whose respective Synapse
93 Synapses; i.e. the count data for a set of Signals. The Generic
111 A pair of quadrature encoding signals are evaluated to determine
135 Any state transition on either quadrature pair signals updates the
167 many Signals may be associated with even a single Count. For example, a
183 In this example, two Signals (quadrature encoder lines A and B) are
188 encoder counter device; the Count, Signals, and Synapses simply
191 Signals associated with the same Count can have differing Synapse action
[all …]
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/include/bits/
H A Dsignum-generic.h37 as of 1003.1-2013, no additional signals have been added by POSIX.
41 Signals in the 1-15 range are defined with their historical numbers.
42 For other signals, we use the BSD numbers.
47 /* ISO C99 signals. */
55 /* Historical signals specified by POSIX. */
68 /* Not all systems support real-time signals. bits/signum.h indicates
71 but some real-time signals may be used internally by glibc. Do not
78 /* Biggest signal number + 1 (including real-time signals). */
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc/usr/include/bits/
H A Dsignum-generic.h37 as of 1003.1-2013, no additional signals have been added by POSIX.
41 Signals in the 1-15 range are defined with their historical numbers.
42 For other signals, we use the BSD numbers.
47 /* ISO C99 signals. */
55 /* Historical signals specified by POSIX. */
68 /* Not all systems support real-time signals. bits/signum.h indicates
71 but some real-time signals may be used internally by glibc. Do not
78 /* Biggest signal number + 1 (including real-time signals). */
/OK3568_Linux_fs/u-boot/arch/arm/mach-socfpga/
H A Dfreeze_controller.c45 * and niotri signals in sys_mgr_frzctrl_freeze_req()
70 * niotri signals in sys_mgr_frzctrl_freeze_req()
79 * assert active low bhniotri & nfrzdrv signals, in sys_mgr_frzctrl_freeze_req()
81 * active high frzreg and nfrzdrv signals in sys_mgr_frzctrl_freeze_req()
95 * active high pllbiasen signals in sys_mgr_frzctrl_freeze_req()
136 * de-assert active low plniotri and niotri signals in sys_mgr_frzctrl_thaw_req()
161 * assert active high pllbiasen signals in sys_mgr_frzctrl_thaw_req()
171 * de-assert active low bhniotri signals, in sys_mgr_frzctrl_thaw_req()
188 /* de-assert active low plniotri and niotri signals */ in sys_mgr_frzctrl_thaw_req()
/OK3568_Linux_fs/kernel/drivers/net/wireless/rsi/
H A DKconfig3 bool "Redpine Signals Inc devices"
16 tristate "Redpine Signals Inc 91x WLAN driver support"
24 bool "Redpine Signals Inc debug support"
32 tristate "Redpine Signals SDIO bus support"
40 tristate "Redpine Signals USB bus support"
48 bool "Redpine Signals WLAN BT Coexistence support"
/OK3568_Linux_fs/kernel/drivers/staging/vc04_services/vchiq-mmal/
H A Dmmal-msg.h220 /* Signals that the current payload is the end of the stream of data */
222 /* Signals that the start of the current payload starts a frame */
224 /* Signals that the end of the current payload ends a frame */
226 /* Signals that the current payload contains only complete frames (>1) */
230 /* Signals that the current payload is a keyframe (i.e. self decodable) */
233 * Signals a discontinuity in the stream of data (e.g. after a seek).
238 * Signals a buffer containing some kind of config data for the component
242 /* Signals an encrypted payload */
244 /* Signals a buffer containing side information */
247 * Signals a buffer which is the snapshot/postview image from a stills
[all …]
/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/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/share/info/
H A Dlibc.info-10301 * NSIG: (libc)Standard Signals.
360 * SIGABRT: (libc)Program Error Signals.
361 * SIGALRM: (libc)Alarm Signals.
362 * SIGBUS: (libc)Program Error Signals.
363 * SIGCHLD: (libc)Job Control Signals.
364 * SIGCLD: (libc)Job Control Signals.
365 * SIGCONT: (libc)Job Control Signals.
366 * SIGEMT: (libc)Program Error Signals.
367 * SIGFPE: (libc)Program Error Signals.
368 * SIGHUP: (libc)Termination Signals.
[all …]
H A Dlibc.info-11301 * NSIG: (libc)Standard Signals.
360 * SIGABRT: (libc)Program Error Signals.
361 * SIGALRM: (libc)Alarm Signals.
362 * SIGBUS: (libc)Program Error Signals.
363 * SIGCHLD: (libc)Job Control Signals.
364 * SIGCLD: (libc)Job Control Signals.
365 * SIGCONT: (libc)Job Control Signals.
366 * SIGEMT: (libc)Program Error Signals.
367 * SIGFPE: (libc)Program Error Signals.
368 * SIGHUP: (libc)Termination Signals.
[all …]
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc/usr/share/info/
H A Dlibc.info-10301 * NSIG: (libc)Standard Signals.
360 * SIGABRT: (libc)Program Error Signals.
361 * SIGALRM: (libc)Alarm Signals.
362 * SIGBUS: (libc)Program Error Signals.
363 * SIGCHLD: (libc)Job Control Signals.
364 * SIGCLD: (libc)Job Control Signals.
365 * SIGCONT: (libc)Job Control Signals.
366 * SIGEMT: (libc)Program Error Signals.
367 * SIGFPE: (libc)Program Error Signals.
368 * SIGHUP: (libc)Termination Signals.
[all …]
H A Dlibc.info-11301 * NSIG: (libc)Standard Signals.
360 * SIGABRT: (libc)Program Error Signals.
361 * SIGALRM: (libc)Alarm Signals.
362 * SIGBUS: (libc)Program Error Signals.
363 * SIGCHLD: (libc)Job Control Signals.
364 * SIGCLD: (libc)Job Control Signals.
365 * SIGCONT: (libc)Job Control Signals.
366 * SIGEMT: (libc)Program Error Signals.
367 * SIGFPE: (libc)Program Error Signals.
368 * SIGHUP: (libc)Termination Signals.
[all …]
/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/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/include/
H A Dsignal.h172 /* Block signals in MASK, returning the old mask. */
175 /* Set the mask of blocked signals to MASK, returning the old mask. */
198 /* Clear all signals from SET. */
201 /* Set all signals in SET. */
231 /* Get and/or change the set of blocked signals. */
235 /* Change the set of blocked signals to SET,
236 wait until a signal arrives, and restore the set of blocked signals.
246 /* Put in SET all signals that are blocked and waiting to be delivered. */
251 /* Select any of pending signals from SET or wait for any to arrive.
260 /* Select any of pending signals from SET and place information in INFO.
[all …]
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc/usr/include/
H A Dsignal.h172 /* Block signals in MASK, returning the old mask. */
175 /* Set the mask of blocked signals to MASK, returning the old mask. */
198 /* Clear all signals from SET. */
201 /* Set all signals in SET. */
231 /* Get and/or change the set of blocked signals. */
235 /* Change the set of blocked signals to SET,
236 wait until a signal arrives, and restore the set of blocked signals.
246 /* Put in SET all signals that are blocked and waiting to be delivered. */
251 /* Select any of pending signals from SET or wait for any to arrive.
260 /* Select any of pending signals from SET and place information in INFO.
[all …]
/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/devicetree/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/devicetree/bindings/arm/
H 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

12345678910>>...76