| /linux/drivers/usb/serial/ |
| H A 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/tools/perf/pmu-events/arch/x86/goldmontplus/ |
| H A D | cache.json | 127 … written the data back to the cache). For example, consider load X and Y, both referencing the sam…
138 …escription": "Counts the number of memory uops retired that is either a loads or a store or both.",
209 … "Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
223 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
234 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
245 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
256 … 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)",
278 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
289 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
[all …]
|
| /linux/tools/perf/pmu-events/arch/x86/goldmont/ |
| H A D | cache.json | 127 … written the data back to the cache). For example, consider load X and Y, both referencing the sam…
138 …escription": "Counts the number of memory uops retired that is either a loads or a store or both.",
209 … "Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
223 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
234 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
245 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
256 …. 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)",
278 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
289 …. Requires MSR_OFFCORE_RESP[0,1] to specify request type and response. (duplicated for both MSRs)",
[all …]
|
| /linux/arch/mips/include/asm/octeon/ |
| H A 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/Documentation/devicetree/bindings/arm/ |
| H A 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/Documentation/power/ |
| H A 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/include/linux/ |
| H A 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
|
| /linux/drivers/usb/gadget/udc/ |
| H A 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
157 supports both full and high speed USB 2.0 data transfers.
169 that supports both full and high speed USB 2.0 data transfers.
181 that supports both host and device switching.
255 # Controllers available in both integrated and discrete versions
263 supports both full and high speed USB 2.0 data transfers.
313 supports both full and high speed USB 2.0 data transfers.
358 supports both full and high speed USB 2.0 data transfers.
[all …]
|
| /linux/Documentation/bpf/ |
| H A D | graph_ds_impl.rst | 36 details in common. Because both have "root"s ("head" for linked_list) and
40 Unless otherwise stated, examples and semantics below apply to both graph data
73 The "root" type for both linked_list and rbtree expects to be in a map_value
74 which also contains a ``bpf_spin_lock`` - in the above example both global
76 spin_lock to be associated with the ``bpf_rb_root`` by virtue of both being in
133 Both the read from and write to ``n->data`` would be rejected. The verifier
139 * Both graph data structures have pointer stability
155 Both terms currently only have meaning in the context of graph nodes and API.
159 Let's enumerate the properties of both types of references.
237 3) n and m are non-owning references, they both point to the same node
[all …]
|
| /linux/tools/perf/pmu-events/arch/arm64/arm/neoverse-v1/ |
| H A D | tlb.json | 16 …accesses, whether the access hits or misses in the TLB. This event counts both demand accesses and…
20 …"PublicDescription": "Counts level 2 TLB refills caused by memory operations from both data and in…
52 …"PublicDescription": "Counts level 2 TLB refills caused by memory read operations from both data a…
56 …tion": "Counts level 2 TLB refills caused by memory write operations from both data and instructio…
60 …tion": "Counts level 2 TLB accesses caused by memory read operations from both data and instructio…
64 …ion": "Counts level 2 TLB accesses caused by memory write operations from both data and instructio…
|
| /linux/tools/perf/pmu-events/arch/arm64/arm/neoverse-n1/ |
| H A D | tlb.json | 16 …accesses, whether the access hits or misses in the TLB. This event counts both demand accesses and…
20 …"PublicDescription": "Counts level 2 TLB refills caused by memory operations from both data and in…
52 …"PublicDescription": "Counts level 2 TLB refills caused by memory read operations from both data a…
56 …tion": "Counts level 2 TLB refills caused by memory write operations from both data and instructio…
60 …tion": "Counts level 2 TLB accesses caused by memory read operations from both data and instructio…
64 …ion": "Counts level 2 TLB accesses caused by memory write operations from both data and instructio…
|
| /linux/arch/mips/cavium-octeon/executive/ |
| H A 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/tools/testing/selftests/net/ |
| H A D | cmsg_ip.sh | 51 for ovr in setsock cmsg both diff; do
61 [ $ovr == "both" ] && m="-F $df -f $df"
84 for ovr in setsock cmsg both diff; do
93 [ $ovr == "both" ] && m="-C $((TOS2)) -c"
111 [ $ovr == "both" ] && m="-C $((TOS )) -c"
138 for ovr in setsock cmsg both diff; do
147 [ $ovr == "both" ] && m="-L $LIM -l"
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | tuner.rst | 35 determined by the current video input. Drivers must support both ioctls
57 A video or radio device cannot support both a tuner and a modulator. Two
69 current video output. Drivers must support both ioctls and set the
81 :ref:`VIDIOC_S_FREQUENCY <VIDIOC_G_FREQUENCY>` ioctl which both take
84 both ioctls when the tuner or modulator ioctls are supported, or when
|
| /linux/arch/riscv/lib/ |
| H A D | memmove.S | 37 * Both Copy Modes: t5 - Inclusive first multibyte/aligned of dest
38 * Both Copy Modes: t6 - Non-Inclusive last multibyte/aligned of dest
39 * Both Copy Modes: t0 - Link / Temporary for load-store
40 * Both Copy Modes: t1 - Temporary for load-store
41 * Both Copy Modes: t2 - Temporary for load-store
42 * Both Copy Modes: a5 - dest to src alignment offset
43 * Both Copy Modes: a6 - Shift ammount
44 * Both Copy Modes: a7 - Inverse Shift ammount
45 * Both Copy Modes: a2 - Alternate breakpoint for unrolled loops
|
| /linux/fs/xfs/scrub/ |
| H A D | tempfile.c | 368 * Begin the process of making changes to both the file being scrubbed and
369 * the temporary file by taking ILOCK_EXCL on both.
380 /* Unlock ILOCK_EXCL on both files. */
409 * mapped to written blocks. The caller must ensure that both inodes are
581 * both the temporary file and the file being scrubbed to the transaction.
582 * This function return with both inodes joined to a new scrub transaction,
623 /* Both files should have the relevant forks. */ in xrep_tempexch_prep_request()
631 /* Exchange all mappings in both forks. */ in xrep_tempexch_prep_request()
654 * temp file. Caller must hold IOLOCK_EXCL but not ILOCK_EXCL on both files.
682 /* Both files have mapped extents; use the regular estimate. */ in xrep_tempexch_estimate()
[all …]
|
| /linux/fs/xfs/ |
| H A D | xfs_exchrange.c | 61 * have flushed both inodes' pagecache and active direct-ios.
108 * this if quota enforcement is disabled or if both inodes' dquots are the
152 * reserve quota for ip2. Then report both. in xfs_exchrange_reserve_quota()
268 /* Update the mtime and ctime of both files. */ in xfs_exchrange_mappings()
295 * be safe because we flushed both files' page caches, exchanged all in xfs_exchrange_mappings()
325 * times of both files as part of the metadata update. The timestamp update
365 * both files. in xfs_exchange_range_checks()
371 * Otherwise we require both ranges to end within EOF. in xfs_exchange_range_checks()
379 * The start of both ranges must be aligned to the file allocation in xfs_exchange_range_checks()
468 /* Wait for the completion of any pending IOs on both files */ in xfs_exchange_range_prep()
[all …]
|
| /linux/arch/mips/math-emu/ |
| H A D | sp_fmax.c | 52 * The case of both inputs quiet NaNs in ieee754sp_fmax()
118 /* Inputs are both positive */ in ieee754sp_fmax()
124 /* Inputs are both negative */ in ieee754sp_fmax()
133 /* Inputs are both positive, with equal signs and exponents */ in ieee754sp_fmax()
138 /* Inputs are both negative, with equal signs and exponents */ in ieee754sp_fmax()
178 * The case of both inputs quiet NaNs in ieee754sp_fmaxa()
|
| H A D | dp_fmin.c | 52 * The case of both inputs quiet NaNs in ieee754dp_fmin()
118 /* Inputs are both positive */ in ieee754dp_fmin()
124 /* Inputs are both negative */ in ieee754dp_fmin()
133 /* Inputs are both positive, with equal signs and exponents */ in ieee754dp_fmin()
138 /* Inputs are both negative, with equal signs and exponents */ in ieee754dp_fmin()
178 * The case of both inputs quiet NaNs in ieee754dp_fmina()
|
| H A D | dp_fmax.c | 52 * The case of both inputs quiet NaNs in ieee754dp_fmax()
118 /* Inputs are both positive */ in ieee754dp_fmax()
124 /* Inputs are both negative */ in ieee754dp_fmax()
133 /* Inputs are both positive, with equal signs and exponents */ in ieee754dp_fmax()
138 /* Inputs are both negative, with equal signs and exponents */ in ieee754dp_fmax()
178 * The case of both inputs quiet NaNs in ieee754dp_fmaxa()
|
| H A D | sp_fmin.c | 52 * The case of both inputs quiet NaNs in ieee754sp_fmin()
118 /* Inputs are both positive */ in ieee754sp_fmin()
124 /* Inputs are both negative */ in ieee754sp_fmin()
133 /* Inputs are both positive, with equal signs and exponents */ in ieee754sp_fmin()
138 /* Inputs are both negative, with equal signs and exponents */ in ieee754sp_fmin()
178 * The case of both inputs quiet NaNs in ieee754sp_fmina()
|
| /linux/fs/pstore/ |
| H A D | Kconfig | 131 NOTE that, both Kconfig and module parameters can configure
142 NOTE that, both Kconfig and module parameters can configure
154 NOTE that, both Kconfig and module parameters can configure
166 NOTE that, both Kconfig and module parameters can configure
178 NOTE that, both Kconfig and module parameters can configure
190 NOTE that, both Kconfig and module parameters can configure
|
| /linux/Documentation/trace/ |
| H A D | fprobe.rst | 84 Also, the unregister_fprobe() will guarantee that the both enter and exit
110 This is the ftrace address of the traced function (both entry and exit).
116 somewhere in the caller. This can be used at both entry and exit.
127 allocated and passed to both `entry_handler` and `exit_handler`.
183 The `fprobe::nmissed` field counts up in both cases. Therefore, the former
184 skips both of entry and exit callback and the latter skips the exit
185 callback, but in both case the counter will increase by 1.
|
| /linux/Documentation/driver-api/hte/ |
| H A D | tegra-hte.rst | 10 (Legacy Interrupt Controller) IRQ GTE. Both GTE instances get the timestamp
21 below. The GPIO GTE code supports both kernel and userspace consumers. The
44 The provider source code of both IRQ and GPIO GTE instances is located at
46 ``drivers/hte/hte-tegra194-test.c`` demonstrates HTE API usage for both IRQ
|
| /linux/Documentation/devicetree/bindings/regulator/ |
| H A D | richtek,rt4801-regulator.yaml | 33 Else if both are specified, DSVP/DSVN could be controlled individually.
34 If this property not specified, treat both as always-on regulators.
53 for controlling both regulators. If this property not specified for
54 any regulator, treat both as always-on regulators.
|