| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/drivers/usb/serial/ |
| D | keyspan_usa26msg.h | 109 name; both meanings are described below.
125 u8 setClocking, // BOTH: host requests baud rate be set
126 baudLo, // BOTH: host does baud divisor calculation
127 baudHi, // BOTH: baudHi is only used for first port (gives lower rates)
134 setLcr, // BOTH: host requests lcr be set
135 lcr, // BOTH: use PARITY, STOPBITS, DATABITS below
137 setFlowControl, // BOTH: host requests flow control be set
138 ctsFlowControl, // BOTH: 1=use CTS flow control, 0=don't
139 xonFlowControl, // BOTH: 1=use XON/XOFF flow control, 0=don't
140 xonChar, // BOTH: specified in current character format
[all …]
|
| /kernel/linux/linux-4.19/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)"
140 …escription": "Counts the number of memory uops retired that is either a loads or a store or both.",
206 … written the data back to the cache). For example, consider load X and Y, both referencing the sam…
227 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
240 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
253 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
266 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
279 … Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
292 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
305 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
[all …]
|
| D | memory.json | 36 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
49 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
62 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
75 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
88 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
101 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
114 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
127 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
140 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
153 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/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
42 both default to "okay". This means the following combinations are
45 /* Neither specified: default to visible in both S and NS */
46 secure-status = "okay"; /* visible in both */
47 status = "okay"; /* visible in both */
48 status = "okay"; secure-status = "okay"; /* visible in both */
52 status = "disabled"; /* disabled in both */
53 status = "disabled"; secure-status = "disabled"; /* disabled in both */
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | debugfs-hisi-sec | 44 Available for both PF and VF, and take no other effect on SEC.
50 Available for both PF and VF, and take no other effect on SEC.
56 Available for both PF and VF, and take no other effect on SEC.
62 Available for both PF and VF, and take no other effect on SEC.
68 Available for both PF and VF, and take no other effect on SEC.
75 Available for both PF and VF, and take no other effect on SEC.
81 Available for both PF and VF, and take no other effect on SEC.
87 Available for both PF and VF, and take no other effect on SEC.
93 Available for both PF and VF, and take no other effect on SEC.
100 Available for both PF and VF, and take no other effect on SEC.
[all …]
|
| D | debugfs-hisi-hpre | 64 Available for both PF and VF, and take no other effect on HPRE.
70 Available for both PF and VF, and take no other effect on HPRE.
76 Available for both PF and VF, and take no other effect on HPRE.
82 Available for both PF and VF, and take no other effect on HPRE.
88 Available for both PF and VF, and take no other effect on HPRE.
95 Available for both PF and VF, and take no other effect on HPRE.
101 Available for both PF and VF, and take no other effect on HPRE.
107 Available for both PF and VF, and take no other effect on HPRE.
114 Available for both PF and VF, and take no other effect on HPRE.
120 Available for both PF and VF, and take no other effect on HPRE.
[all …]
|
| D | debugfs-hisi-zip | 57 Available for both PF and VF, and take no other effect on ZIP.
63 Available for both PF and VF, and take no other effect on ZIP.
69 Available for both PF and VF, and take no other effect on ZIP.
75 Available for both PF and VF, and take no other effect on ZIP.
81 Available for both PF and VF, and take no other effect on ZIP.
88 Available for both PF and VF, and take no other effect on ZIP.
94 Available for both PF and VF, and take no other effect on ZIP.
100 Available for both PF and VF, and take no other effect on ZIP.
107 Available for both PF and VF, and take no other effect on ZIP.
114 Available for both PF and VF, and take no other effect on ZIP.
|
| /kernel/linux/linux-4.19/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)"
160 …escription": "Counts the number of memory uops retired that is either a loads or a store or both.",
232 … written the data back to the cache). For example, consider load X and Y, both referencing the sam…
255 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
270 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
285 … Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
300 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
315 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
330 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
345 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/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 */
|
| /kernel/linux/linux-4.19/Documentation/power/ |
| D | apm-acpi.txt | 11 build a kernel with both ACPI and APM enabled (as of 2.3.x ACPI is
16 No, sorry, you cannot have both ACPI and APM enabled and running at
18 would like to use both to get a full set of working features, but you
24 Both APM and ACPI rely on user-space daemons, apmd and acpid
25 respectively, to be completely functional. Obtain both of these
28 Go ahead and start both. If ACPI or APM is not available on your
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/drivers/usb/musb/ |
| D | Kconfig | 16 or the USB host role, or both.
57 both host and gadget features are enabled.
88 depends on NOP_USB_XCEIV = USB_MUSB_HDRC # both built-in or both modules
161 depends on USB_MUSB_TUSB6010 = USB_MUSB_HDRC # both built-in or both modules
|
| /kernel/linux/linux-5.10/tools/testing/selftests/kvm/x86_64/ |
| D | tsc_msrs_test.c | 37 /* Guest: writes to MSR_IA32_TSC affect both MSRs. */ in guest_code()
43 /* Guest: writes to MSR_IA32_TSC_ADJUST affect both MSRs. */ in guest_code()
57 * host-side offset and affect both MSRs. in guest_code()
66 * Guest: writes to MSR_IA32_TSC affect both MSRs, so the host-side in guest_code()
116 /* Guest: writes to MSR_IA32_TSC affect both MSRs. */ in main()
122 /* Guest: writes to MSR_IA32_TSC_ADJUST affect both MSRs. */ in main()
149 * host-side offset and affect both MSRs. in main()
157 * Guest: writes to MSR_IA32_TSC affect both MSRs, so the host-side in main()
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | iocontext.h | 20 * ->icq_align. Both size and align must be larger than that of struct
44 * called and, on destruction, ->elevator_exit_icq_fn(). Both functions
45 * are called with both the associated io_context and queue locks held.
52 * As icq's are linked from both ioc and q, the locking rules are a bit
61 * itself is protected by q lock. However, both the indexes and icq
69 * - Linking and unlinking icq's are performed while holding both ioc and q
79 * respectively. Both fields are unused once ioc_exit_icq() is
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | iocontext.h | 20 * ->icq_align. Both size and align must be larger than that of struct
44 * called and, on destruction, ->elevator_exit_icq_fn(). Both functions
45 * are called with both the associated io_context and queue locks held.
52 * As icq's are linked from both ioc and q, the locking rules are a bit
61 * itself is protected by q lock. However, both the indexes and icq
69 * - Linking and unlinking icq's are performed while holding both ioc and q
79 * respectively. Both fields are unused once ioc_exit_icq() is
|
| /kernel/linux/linux-5.10/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
166 depends on USB_MUSB_TUSB6010 = USB_MUSB_HDRC # both built-in or both modules
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/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
|
| /kernel/linux/linux-4.19/drivers/usb/gadget/udc/ |
| D | Kconfig | 10 # - Some systems have both kinds of controllers.
13 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
22 # - licensed IP used in both SOC and discrete versions
173 supports both full and high speed USB 2.0 data transfers.
185 that supports both full and high speed USB 2.0 data transfers.
289 # Controllers available in both integrated and discrete versions
297 supports both full and high speed USB 2.0 data transfers.
346 both full and high speed USB 2.0 data transfers.
369 supports both full and high speed USB 2.0 data transfers.
414 supports both full and high speed USB 2.0 data transfers.
[all …]
|
| /kernel/linux/linux-5.10/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.
349 both full and high speed USB 2.0 data transfers.
372 supports both full and high speed USB 2.0 data transfers.
417 supports both full and high speed USB 2.0 data transfers.
[all …]
|