| /Linux-v5.4/drivers/usb/serial/ |
| D | keyspan_usa26msg.h | 110 name; both meanings are described below.
126 u8 setClocking, // BOTH: host requests baud rate be set
127 baudLo, // BOTH: host does baud divisor calculation
128 baudHi, // BOTH: baudHi is only used for first port (gives lower rates)
135 setLcr, // BOTH: host requests lcr be set
136 lcr, // BOTH: use PARITY, STOPBITS, DATABITS below
138 setFlowControl, // BOTH: host requests flow control be set
139 ctsFlowControl, // BOTH: 1=use CTS flow control, 0=don't
140 xonFlowControl, // BOTH: 1=use XON/XOFF flow control, 0=don't
141 xonChar, // BOTH: specified in current character format
[all …]
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/goldmont/ |
| D | cache.json | 69 …: "Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)"
146 …escription": "Counts the number of memory uops retired that is either a loads or a store or both.",
218 … written the data back to the cache). For example, consider load X and Y, both referencing the sam…
241 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
254 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
267 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
280 … Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
293 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
306 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
319 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
[all …]
|
| /Linux-v5.4/tools/perf/pmu-events/arch/x86/goldmontplus/ |
| D | cache.json | 83 …: "Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)"
166 …escription": "Counts the number of memory uops retired that is either a loads or a store or both.",
244 … written the data back to the cache). For example, consider load X and Y, both referencing the sam…
269 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
284 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
299 … Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
314 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
329 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
344 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
359 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
[all …]
|
| /Linux-v5.4/arch/mips/include/asm/octeon/ |
| D | cvmx-spi.h | 89 * can operate as a full duplex (both Tx and Rx data paths
91 * active or the Rx data path is active, but not both).
107 * can operate as a full duplex (both Tx and Rx data paths
109 * active or the Rx data path is active, but not both).
176 * can operate as a full duplex (both Tx and Rx data paths
178 * active or the Rx data path is active, but not both).
192 * can operate as a full duplex (both Tx and Rx data paths
194 * active or the Rx data path is active, but not both).
209 * can operate as a full duplex (both Tx and Rx data paths
211 * active or the Rx data path is active, but not both).
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/arm/ |
| D | secure.txt | 9 space, or visible in both. (One example of that situation would be a
32 secure- bindings only need to be used where both the Secure and Normal
43 both default to "okay". This means the following combinations are
46 /* Neither specified: default to visible in both S and NS */
47 secure-status = "okay"; /* visible in both */
48 status = "okay"; /* visible in both */
49 status = "okay"; secure-status = "okay"; /* visible in both */
53 status = "disabled"; /* disabled in both */
54 status = "disabled"; secure-status = "disabled"; /* disabled in both */
|
| /Linux-v5.4/Documentation/power/ |
| D | apm-acpi.rst | 13 build a kernel with both ACPI and APM enabled (as of 2.3.x ACPI is
18 No, sorry, you cannot have both ACPI and APM enabled and running at
20 would like to use both to get a full set of working features, but you
26 Both APM and ACPI rely on user-space daemons, apmd and acpid
27 respectively, to be completely functional. Obtain both of these
30 Go ahead and start both. If ACPI or APM is not available on your
|
| /Linux-v5.4/include/linux/ |
| D | iocontext.h | 19 * ->icq_align. Both size and align must be larger than that of struct
43 * called and, on destruction, ->elevator_exit_icq_fn(). Both functions
44 * are called with both the associated io_context and queue locks held.
51 * As icq's are linked from both ioc and q, the locking rules are a bit
60 * itself is protected by q lock. However, both the indexes and icq
68 * - Linking and unlinking icq's are performed while holding both ioc and q
78 * respectively. Both fields are unused once ioc_exit_icq() is
|
| /Linux-v5.4/drivers/usb/musb/ |
| D | Kconfig | 17 or the USB host role, or both.
58 both host and gadget features are enabled.
89 depends on NOP_USB_XCEIV = USB_MUSB_HDRC # both built-in or both modules
162 depends on USB_MUSB_TUSB6010 = USB_MUSB_HDRC # both built-in or both modules
|
| /Linux-v5.4/Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl-zx.txt | 5 main controller is TOP_PMM and the auxiliary one is AON_IOCFG. Both
38 'TOP pins'. For pins like KEY_ROW2, the pinmux is controlled by both
40 the pin spread in both controllers. This type of pins are called 'AON pins'.
41 Though pinmux implementation is quite different, pinconf is same for both
42 types of pins. Both are controlled by auxiliary controller, i.e. AON_IOCFG
|
| /Linux-v5.4/drivers/usb/gadget/udc/ |
| D | Kconfig | 11 # - Some systems have both kinds of controllers.
14 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
23 # - licensed IP used in both SOC and discrete versions
175 supports both full and high speed USB 2.0 data transfers.
187 that supports both full and high speed USB 2.0 data transfers.
291 # Controllers available in both integrated and discrete versions
299 supports both full and high speed USB 2.0 data transfers.
348 both full and high speed USB 2.0 data transfers.
371 supports both full and high speed USB 2.0 data transfers.
416 supports both full and high speed USB 2.0 data transfers.
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/input/ |
| D | gpio-keys.txt | 20 both at the same time. Specifying both properties is allowed.
30 system when asserted, when deasserted, or both. This property is
36 EV_ACT_ANY - both asserted and deasserted
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | tuner.rst | 42 determined by the current video input. Drivers must support both ioctls
64 A video or radio device cannot support both a tuner and a modulator. Two
76 current video output. Drivers must support both ioctls and set the
88 :ref:`VIDIOC_S_FREQUENCY <VIDIOC_G_FREQUENCY>` ioctl which both take
91 both ioctls when the tuner or modulator ioctls are supported, or when
|
| D | dev-subdev.rst | 29 make them directly configurable by applications. When both the
51 of hardware. This situation is common in embedded platforms, where both
103 :ref:`pipeline-scaling`, where image scaling can be performed on both
150 pipeline, acceptable to both application and driver, can't rely on
160 untouched (this applies to both the software state stored in the driver
202 Applications must then take care to configure both ends of every link
341 (or possible even on both). Cropping is used to select the area of
348 left corner and the rectangle size. Both the coordinates and sizes are
362 from the original and scaled image sizes. Both sizes are represented by
375 COMPOSE rectangle on the sink pad. In both sink and source pads, the
[all …]
|
| /Linux-v5.4/drivers/net/wireless/cisco/ |
| D | Kconfig | 30 This driver support both the standard Linux Wireless Extensions
31 and Cisco proprietary API, so both the Linux Wireless Tools and the
55 This driver support both the standard Linux Wireless Extensions
56 and Cisco proprietary API, so both the Linux Wireless Tools and the
|
| /Linux-v5.4/arch/mips/cavium-octeon/executive/ |
| D | cvmx-spi.c | 97 * can operate as a full duplex (both Tx and Rx data paths
99 * active or the Rx data path is active, but not both).
143 * can operate as a full duplex (both Tx and Rx data paths
145 * active or the Rx data path is active, but not both).
188 * can operate as a full duplex (both Tx and Rx data paths
190 * active or the Rx data path is active, but not both).
303 * can operate as a full duplex (both Tx and Rx data paths
305 * active or the Rx data path is active, but not both).
422 * can operate as a full duplex (both Tx and Rx data paths
424 * active or the Rx data path is active, but not both).
[all …]
|
| /Linux-v5.4/tools/testing/selftests/firmware/ |
| D | fw_filesystem.sh | 325 if [ "$2" = "both" ]; then
389 # test with both files present
393 echo "Testing with both plain and xz files present..."
395 test_batched_request_firmware $i both
399 test_batched_request_firmware_into_buf $i both
403 test_batched_request_firmware_direct $i both
407 test_request_firmware_nowait_uevent $i both
411 test_request_firmware_nowait_custom $i both
|
| /Linux-v5.4/arch/mips/math-emu/ |
| D | sp_fmax.c | 52 * The case of both inputs quiet NaNs in ieee754sp_fmax()
119 /* Inputs are both positive */ in ieee754sp_fmax()
125 /* Inputs are both negative */ in ieee754sp_fmax()
134 /* Inputs are both positive, with equal signs and exponents */ in ieee754sp_fmax()
139 /* Inputs are both negative, with equal signs and exponents */ in ieee754sp_fmax()
179 * The case of both inputs quiet NaNs in ieee754sp_fmaxa()
|
| D | sp_fmin.c | 52 * The case of both inputs quiet NaNs in ieee754sp_fmin()
119 /* Inputs are both positive */ in ieee754sp_fmin()
125 /* Inputs are both negative */ in ieee754sp_fmin()
134 /* Inputs are both positive, with equal signs and exponents */ in ieee754sp_fmin()
139 /* Inputs are both negative, with equal signs and exponents */ in ieee754sp_fmin()
179 * The case of both inputs quiet NaNs in ieee754sp_fmina()
|
| D | dp_fmax.c | 52 * The case of both inputs quiet NaNs in ieee754dp_fmax()
119 /* Inputs are both positive */ in ieee754dp_fmax()
125 /* Inputs are both negative */ in ieee754dp_fmax()
134 /* Inputs are both positive, with equal signs and exponents */ in ieee754dp_fmax()
139 /* Inputs are both negative, with equal signs and exponents */ in ieee754dp_fmax()
179 * The case of both inputs quiet NaNs in ieee754dp_fmaxa()
|
| D | dp_fmin.c | 52 * The case of both inputs quiet NaNs in ieee754dp_fmin()
119 /* Inputs are both positive */ in ieee754dp_fmin()
125 /* Inputs are both negative */ in ieee754dp_fmin()
134 /* Inputs are both positive, with equal signs and exponents */ in ieee754dp_fmin()
139 /* Inputs are both negative, with equal signs and exponents */ in ieee754dp_fmin()
179 * The case of both inputs quiet NaNs in ieee754dp_fmina()
|
| /Linux-v5.4/Documentation/devicetree/bindings/regmap/ |
| D | regmap.txt | 16 On SoCs that can be operated in both big-endian and little-endian
17 modes, with a single hardware switch controlling both the endianness
20 blob in both cases.
|
| /Linux-v5.4/tools/testing/selftests/media_tests/ |
| D | media_dev_allocator.sh | 18 echo "Test unbind both devices - start"
33 echo "Test unbind both devices - end"
37 echo "Test bind both devices - start"
50 echo "Test bind both devices - end"
|
| /Linux-v5.4/Documentation/devicetree/bindings/sound/ |
| D | fsl-sai.txt | 40 with Rx) which means both the transmitter and the
46 means both transmitter and receiver will send and
61 - If both fsl,sai-asynchronous and fsl,sai-synchronous-rx are absent, the
62 default synchronous mode (sync Rx with Tx) will be used, which means both
|
| /Linux-v5.4/arch/mips/kvm/ |
| D | 00README.txt | 9 (2) Both Guest kernel and Guest Userspace execute in UM.
16 (2) 16K Page Sizes: Both Host Kernel and Guest Kernel should have the same page size, currently at …
20 Both the host kernel and Guest kernel should have the page size set to 16K.
|
| /Linux-v5.4/Documentation/networking/dsa/ |
| D | lan9303.rst | 18 The LAN9303 can be managed both via MDIO and I2C, both supported by this driver.
24 When both user ports are joined to the same bridge, the normal HW MAC learning
|
