| /Linux-v5.10/arch/arm/mach-spear/ |
| D | pl080.c | 28 } 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-v5.10/tools/testing/selftests/arm64/fp/ |
| D | README | 30 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-v5.10/drivers/net/wireless/rsi/ |
| D | Kconfig | 3 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"
|
| /Linux-v5.10/Documentation/driver-api/ |
| D | generic-counter.rst | 80 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 …]
|
| D | hsi.rst | 15 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.
|
| /Linux-v5.10/Documentation/trace/coresight/ |
| D | coresight-ect.rst | 14 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-v5.10/drivers/staging/vc04_services/vchiq-mmal/ |
| D | mmal-msg.h | 220 /* 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 …]
|
| /Linux-v5.10/arch/mips/include/asm/mach-rc32434/ |
| D | gpio.h | 39 /* UART GPIO signals */
45 /* M & P bus GPIO signals */
51 /* CPU GPIO signals */
54 /* Reserved GPIO signals */
63 /* NAND GPIO signals */
|
| /Linux-v5.10/Documentation/devicetree/bindings/gpio/ |
| D | nvidia,tegra186-gpio.txt | 10 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
|
| D | gpio-eic-sprd.txt | 11 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.
|
| /Linux-v5.10/Documentation/devicetree/bindings/display/panel/ |
| D | panel-common.yaml | 105 # and timing of those control signals are device-specific and left for panel
107 # used for panels that implement compatible control signals.
116 signals (or active high power down signals) can be supported by inverting
127 while active. Active high reset signals can be supported by inverting the
134 The tearing effect signal is active high. Active low signals can be
152 # backlight control through GPIO, PWM or other signals connected to an external
|
| /Linux-v5.10/Documentation/devicetree/bindings/arm/ |
| D | coresight-cti.yaml | 20 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-v5.10/Documentation/devicetree/bindings/reset/ |
| D | reset.txt | 3 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-v5.10/drivers/hwtracing/coresight/ |
| D | coresight-cti.h | 54 * CTI CSSoc 600 has a max of 32 trigger signals per direction.
62 * Group of related trigger signals
64 * @nr_sigs: number of signals in the group.
66 * @sig_types: array of types for the signals, length nr_sigs.
76 * lists input and output trigger signals for the device
78 * @con_in: connected CTIIN signals for the device.
79 * @con_out: connected CTIOUT signals for the device.
118 * @nr_trig_max: Max number of trigger signals implemented on device.
|
| /Linux-v5.10/arch/um/os-Linux/ |
| D | signal.c | 44 /* enable signals if sig isn't IRQ signal */ in sig_handler_common()
54 * These are the asynchronous signals. SIGPROF is excluded because we want to
184 * Again, pending comes back with a mask of signals in hard_handler()
241 * This must return with signals disabled, so this barrier in block_signals()
265 * Save and reset save_pending after enabling signals. This in unblock_signals()
280 * We have pending interrupts, so disable signals, as the in unblock_signals()
285 * pending signals will mess up the tracing state. in unblock_signals()
311 /* Re-enable signals and trace that we're doing so. */ in unblock_signals()
|
| /Linux-v5.10/drivers/reset/ |
| D | reset-imx7.c | 25 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()
|
| D | Kconfig | 82 Say Y to control the reset signals provided by reset controller.
132 reset signals provided by AOSS for Modem, Venus, ADSP,
141 to control reset signals provided by PDC for Modem, Compute,
164 firmware controlling all the reset signals.
229 Say Y if you want to control reset signals provided by System Control
239 on UniPhier SoCs. Say Y if you want to control reset signals
|
| /Linux-v5.10/include/linux/clk/ |
| D | analogbits-wrpll-cln28hpc.h | 38 * @divr: reference divider value (6 bits), as presented to the PLL signals
39 * @divf: feedback divider value (9 bits), as presented to the PLL signals
40 * @divq: output divider value (3 bits), as presented to the PLL signals
49 * on its input signals. Thus @divr and @divf are the actual divisors
|
| /Linux-v5.10/tools/testing/selftests/arm64/signal/ |
| D | README | 4 Signals Tests
12 is described (and configured) using the descriptor signals.h::struct tdescr
24 - Signals' test-cases hereafter defined belong currently to two
48 expecting), using the same logic/perspective as in the arm64 Kernel signals
|
| /Linux-v5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-coresight-devices-cti | 35 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-v5.10/Documentation/userspace-api/media/v4l/ |
| D | yuv-formats.rst | 9 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
|
| /Linux-v5.10/tools/lib/subcmd/ |
| D | sigchain.c | 13 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-v5.10/drivers/pinctrl/aspeed/ |
| D | pinmux-aspeed.h | 20 * Further, not all signals can be unmuxed, as some expressions depend on
39 * C5 is a multi-signal pin (high and low priority signals). Here we touch
57 * bit in the STRAP register. The ACPI bit configures signals on pins in
78 * selecting the signals on pin E18)
119 * signals, but is used to decent effect with some of the UARTs where not all
120 * signals are required. However, this isn't done consistently - UART1 is
121 * enabled on a per-pin basis, and by contrast, all signals for UART6 are
124 * Further, the high and low priority signals listed in the table above share
125 * a configuration bit. The VPI signals should operate in concert in a single
126 * function, but the UART signals should retain the ability to be configured
[all …]
|
| /Linux-v5.10/include/trace/events/ |
| D | signal.h | 91 * Note that some signals reported by signal_generate tracepoint can be
93 * This means, this can show which signals are actually delivered, but
94 * matching generated signals and delivered signals may not be correct.
|
| /Linux-v5.10/Documentation/devicetree/bindings/leds/ |
| D | leds-bcm6328.txt | 16 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
|
