Home
last modified time | relevance | path

Searched full:between (Results 1 – 25 of 4546) sorted by relevance

12345678910>>...182

/Linux-v5.10/drivers/mailbox/
DKconfig5 Mailbox is a framework to control hardware communication between
41 send short messages between Highbank's A9 cores and the EnergyCore
78 between CPU cores and MCU processor on Some Rockchip SOCs.
88 between the OS and a platform such as the BMC. This medium
99 to send message between processors. Say Y here if you want to use the
124 and K3 architecture SoCs. These may be used for communication between
135 between application processors and other processors/MCU/DSP. Select
145 between application processors and MCU. Say Y here if you want to
169 between different remote processors and host processors on Tegra186
178 Mailbox (IPCM) between the ARM 64-bit cores and SLIMpro controller.
[all …]
/Linux-v5.10/drivers/media/cec/platform/
DKconfig15 between compatible devices.
41 between compatible devices.
53 between compatible devices.
64 between compatible devices.
75 between compatible devices.
87 between compatible devices.
98 between compatible devices.
110 between compatible devices.
/Linux-v5.10/tools/testing/selftests/net/forwarding/
Dtc_vlan_modify.sh108 check_fail $? "ping between two different vlans passed when should not"
111 check_fail $? "ping6 between two different vlans passed when should not"
119 check_err $? "ping between two different vlans failed when should not"
122 check_err $? "ping6 between two different vlans failed when should not"
135 check_fail $? "ping between two different vlans passed when should not"
138 check_fail $? "ping6 between two different vlans passed when should not"
146 check_err $? "ping between two different vlans failed when should not"
149 check_err $? "ping6 between two different vlans failed when should not"
/Linux-v5.10/net/dccp/ccids/lib/
Dpacket_history.c157 if (!dccp_loss_free(s0, s1, n1)) { /* gap between S0 and S1 */ in __do_track_loss()
185 /* gap between S2 and S1: just update loss_prev */ in __one_after_loss()
188 } else { /* gap between S0 and S2 */ in __one_after_loss()
190 * Reorder history to insert S2 between S0 and S1 in __one_after_loss()
217 * Reorder history to insert S3 between S1 and S2 in __two_after_loss()
231 /* hole between S0 and S1 filled by S3 */ in __two_after_loss()
239 /* gap remains between S1 and S2 */ in __two_after_loss()
244 } else /* gap exists between S3 and S1, loss_count stays at 2 */ in __two_after_loss()
251 * The remaining case: S0 < S3 < S1 < S2; gap between S0 and S3 in __two_after_loss()
252 * Reorder history to insert S3 between S0 and S1. in __two_after_loss()
[all …]
/Linux-v5.10/include/linux/
Dpercpu-refcount.h10 * There's one important difference between percpu refs and normal atomic_t
145 * There are no implied RCU grace periods between kill and release.
168 * between contaminating the pointer value, meaning that in __ref_is_percpu()
196 * This function is safe to call as long as @ref is between init and exit.
218 * This function is safe to call as long as @ref is between init and exit.
233 * This function is safe to call as long as @ref is between init and exit.
262 * This function is safe to call as long as @ref is between init and exit.
282 * This function is safe to call as long as @ref is between init and exit.
311 * This function is safe to call as long as @ref is between init and exit.
334 * This function is safe to call as long as @ref is between init and exit.
[all …]
Ddim.h14 * Number of events between DIM iterations.
20 * Is a difference between values justifies taking an action.
27 * Calculate the gap between two values.
35 * Used for communications between DIM and its consumer.
51 * Used for communications between DIM and its consumer.
232 * dim_calc_stats - calculate the difference between two samples
235 * @curr_stats: delta between samples
237 * Calculate the delta between two samples (in data rates).
/Linux-v5.10/drivers/clk/zynqmp/
Dpll.c15 * @hw: Handle between common and hardware-specific interfaces
42 * @hw: Handle between common and hardware-specific interfaces
64 * @hw: Handle between common and hardware-specific interfaces
88 * @hw: Handle between common and hardware-specific interfaces
124 * @hw: Handle between common and hardware-specific interfaces
158 * @hw: Handle between common and hardware-specific interfaces
208 * @hw: Handle between common and hardware-specific interfaces
232 * @hw: Handle between common and hardware-specific interfaces
256 * @hw: Handle between common and hardware-specific interfaces
/Linux-v5.10/Documentation/devicetree/bindings/memory-controllers/
Dti-aemif.txt96 Time between the end of one asynchronous memory
99 between a read followed by read or a write
103 Time between the beginning of a memory cycle
108 Time between the activation and deactivation of
113 Time between the deactivation of the read
120 Time between the beginning of a memory cycle
125 Time between the activation and deactivation of
130 Time between the deactivation of the write
/Linux-v5.10/Documentation/ABI/testing/
Dsysfs-bus-iio-adc-hi843523 The low voltage threshold range is between 2..21V.
24 Hysteresis between low and high thresholds can not be lower then 2 and
43 The high voltage threshold range is between 3..22V.
44 Hysteresis between low and high thresholds can not be lower then 2 and
Dsysfs-class-backlight-adp552017 is an input code between 0 and 127, which is transformed to a
18 value between 0 mA and 30 mA using linear or non-linear
30 input code between 0 and 127, which is transformed to a value
31 between 0 mA and 30 mA using linear or non-linear algorithms.
Dsysfs-class-backlight-adp886022 is an input code between 0 and 127, which is transformed to a
23 value between 0 mA and 30 mA using linear or non-linear
36 input code between 0 and 127, which is transformed to a value
37 between 0 mA and 30 mA using linear or non-linear algorithms.
/Linux-v5.10/drivers/dma-buf/
DKconfig11 userspace via Sync File fds for synchronization between drivers via
43 bool "Move notify between drivers (EXPERIMENTAL)"
51 execution context and memory management between drivers.
65 between drivers.
/Linux-v5.10/drivers/staging/media/atomisp/pci/isp/kernels/tnr/tnr_1.0/
Dia_css_tnr_types.h25 * When difference between current frame and previous frame is less than or
28 * When difference between current frame and previous frame is greater
46 If difference between current frame and
52 If difference between current frame and
/Linux-v5.10/Documentation/input/
Dmulti-touch-protocol.rst53 The main difference between the stateless type A protocol and the stateful
107 raw data for all present contacts are sent between every synchronization
189 indicate the distance between the contact and the surface.
264 The distance, in surface units, between the contact and the surface. Zero
285 support is possible if the device can distinguish between the two axis, but
286 not (uniquely) any values in between. In such cases, the range of
297 the device cannot distinguish between the intended touch point and the
302 device cannot distinguish between the intended touch point and the tool
312 between different tool types, such as a finger or a pen. In such cases, the
352 the device can distinguish between a finger along the Y axis (0) and a
[all …]
/Linux-v5.10/drivers/net/ethernet/freescale/
Ducc_geth.h63 frames) transmitted that were between
67 frames) transmitted that were between 128
73 frames) received that were between MINLength
76 frames) received that were between 128
497 u32 txpkts256; /* total packets (including bad) between 256
499 u32 txpkts512; /* total packets (including bad) between 512
501 u32 txpkts1024; /* total packets (including bad) between 1024
503 u32 txpktsjumbo; /* total packets (including bad) between 1024
521 u32 pkts256; /* total frames (including bad) between 256 and
523 u32 pkts512; /* total frames (including bad) between 512 and
[all …]
/Linux-v5.10/drivers/clk/zynq/
Dpll.c16 * @hw: Handle between common and hardware-specific interfaces
46 * @hw: Handle between common and hardware-specific interfaces
67 * @hw: Handle between common and hardware-specific interfaces
89 * @hw: Handle between common and hardware-specific interfaces
112 * @hw: Handle between common and hardware-specific interfaces
142 * @hw: Handle between common and hardware-specific interfaces
/Linux-v5.10/drivers/misc/cxl/
Dhcalls.h93 * are between 0 and (ibm,error-buffer-size - 1)
103 * between 0 and (ibm,#config-records - 1)
105 * valid values are between 0 and (ibm,config-record-size - 1)
122 * Parameter1 = # of VPD record to retrieve, valid values are between 0
127 * values are between 0 and 256
180 * values are between 0 and 256
/Linux-v5.10/Documentation/devicetree/bindings/
Dgraph.txt7 control flow to devices, but there can be more complex connections between
10 There already is a simple directed graph between devices tree nodes using
23 Here the ports describe data interfaces, and the links between them are
87 Links between endpoints
94 their 'remote-endpoint' phandles pointing at each other form a link between the
/Linux-v5.10/drivers/net/ethernet/atheros/atl1e/
Datl1e.h259 …unsigned long rx_sz_65_127; /* The number of good and bad packets received that are between 65 a…
260 …unsigned long rx_sz_128_255; /* The number of good and bad packets received that are between 128 …
261 …unsigned long rx_sz_256_511; /* The number of good and bad packets received that are between 256 …
262 …unsigned long rx_sz_512_1023; /* The number of good and bad packets received that are between 512 …
263 …unsigned long rx_sz_1024_1518; /* The number of good and bad packets received that are between
264 …unsigned long rx_sz_1519_max; /* The number of good and bad packets received that are between 1519…
283 …unsigned long tx_sz_65_127; /* The number of good and bad packets transmitted that are between 6…
284 …unsigned long tx_sz_128_255; /* The number of good and bad packets transmitted that are between 1…
285 …unsigned long tx_sz_256_511; /* The number of good and bad packets transmitted that are between 2…
286 …unsigned long tx_sz_512_1023; /* The number of good and bad packets transmitted that are between 5…
[all …]
/Linux-v5.10/Documentation/userspace-api/media/v4l/
Dfield-order.rst9 We have to distinguish between progressive and interlaced video.
13 odd and even field are transmitted, and due to a small delay between
23 object on screen may well move between one field and the next. For
29 combine to frames. We distinguish between top (aka odd) and bottom (aka
43 determined by the video standard. Hence the distinction between temporal
127 any dropped fields between them (fields can drop individually),
/Linux-v5.10/Documentation/devicetree/bindings/arm/
Dcoresight-cti.yaml18 The CTI component properties define the connections between the individual
31 In general the connections between CTI and components via the trigger signals
36 between CTI and the CPU core and ETM if present. In the case of a v8
45 on the connections between the CTI and other components for correct operation.
49 between CTI and other CoreSight components.
51 Certain triggers between CoreSight devices and the CTI have specific types
107 propagated between sockets.
133 between this CTI and another hardware device. This device may be a CPU,
/Linux-v5.10/Documentation/devicetree/bindings/dma/
Dst,stm32-dma.yaml20 0x0: no address increment between transfers
21 0x1: increment address between transfers
23 0x0: no address increment between transfers
24 0x1: increment address between transfers
/Linux-v5.10/fs/xfs/
Dxfs_sysctl.h27 xfs_sysctl_val_t syncd_timer; /* Interval between xfssyncd wakeups */
32 xfs_sysctl_val_t xfs_buf_timer; /* Interval between xfsbufd wakeups. */
38 xfs_sysctl_val_t eofb_timer; /* Interval between eofb scan wakeups */
39 xfs_sysctl_val_t cowb_timer; /* Interval between cowb scan wakeups */
/Linux-v5.10/Documentation/devicetree/bindings/mtd/
Dcadence-quadspi.txt29 mode chip select outputs are de-asserted between
31 - cdns,tsd2d-ns : Delay in nanoseconds between one chip select being
33 - cdns,tchsh-ns : Delay in nanoseconds between last bit of current
36 - cdns,tslch-ns : Delay in nanoseconds between setting qspi_n_ss_out low
/Linux-v5.10/include/linux/sched/
Dsd_flags.h40 * involves equalizing a metric between groups), or for flags describing some
41 * shared resource (which would be shared between groups).
89 * NEEDS_GROUPS: Per-CPU capacity is asymmetric between groups.
98 * NEEDS_GROUPS: Capacity is shared between groups.
107 * NEEDS_GROUPS: Caches are shared between groups.

12345678910>>...182