| /kernel/linux/linux-5.10/drivers/mailbox/ |
| D | Kconfig | 5 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 …]
|
| /kernel/linux/linux-4.19/drivers/mailbox/ |
| D | Kconfig | 4 Mailbox is a framework to control hardware communication between
40 send short messages between Highbank's A9 cores and the EnergyCore
67 between CPU cores and MCU processor on Some Rockchip SOCs.
77 between the OS and a platform such as the BMC. This medium
88 to send message between processors. Say Y here if you want to use the
113 architecture SoCs. These may be used for communication between
124 between application processors and other processors/MCU/DSP. Select
134 between application processors and MCU. Say Y here if you want to
158 between different remote processors and host processors on Tegra186
167 Mailbox (IPCM) between the ARM 64-bit cores and SLIMpro controller.
[all …]
|
| /kernel/linux/linux-5.10/drivers/media/cec/platform/ |
| D | Kconfig | 15 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.
|
| /kernel/linux/linux-5.10/tools/testing/selftests/net/forwarding/ |
| D | tc_vlan_modify.sh | 108 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"
|
| /kernel/linux/linux-5.10/net/dccp/ccids/lib/ |
| D | packet_history.c | 157 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 …]
|
| /kernel/linux/linux-4.19/net/dccp/ccids/lib/ |
| D | packet_history.c | 170 if (!dccp_loss_free(s0, s1, n1)) { /* gap between S0 and S1 */ in __do_track_loss()
198 /* gap between S2 and S1: just update loss_prev */ in __one_after_loss()
201 } else { /* gap between S0 and S2 */ in __one_after_loss()
203 * Reorder history to insert S2 between S0 and S1 in __one_after_loss()
230 * Reorder history to insert S3 between S1 and S2 in __two_after_loss()
244 /* hole between S0 and S1 filled by S3 */ in __two_after_loss()
252 /* gap remains between S1 and S2 */ in __two_after_loss()
257 } else /* gap exists between S3 and S1, loss_count stays at 2 */ in __two_after_loss()
264 * The remaining case: S0 < S3 < S1 < S2; gap between S0 and S3 in __two_after_loss()
265 * Reorder history to insert S3 between S0 and S1. in __two_after_loss()
[all …]
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | percpu-refcount.h | 10 * There's one important difference between percpu refs and normal atomic_t
123 * There are no implied RCU grace periods between kill and release.
146 * between contaminating the pointer value, meaning that in __ref_is_percpu()
174 * This function is safe to call as long as @ref is between init and exit.
196 * This function is safe to call as long as @ref is between init and exit.
210 * This function is safe to call as long as @ref is between init and exit.
244 * This function is safe to call as long as @ref is between init and exit.
273 * This function is safe to call as long as @ref is between init and exit.
296 * This function is safe to call as long as @ref is between init and exit.
309 * This function is safe to call as long as @ref is between init and exit
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-class-backlight-driver-adp8870 | 12 on this <backlight>. Values are between 0 and 127. This file
26 on this <backlight>. Values are between 0 and 127, typically
38 is enabled). Returns integer between 0 (dark) and
47 integer between 1..5 (1 = daylight, 2 = bright, ..., 5 = dark).
48 Writing a value between 1..5 forces the backlight controller
|
| D | sysfs-class-backlight-adp5520 | 17 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.
|
| D | sysfs-bus-iio-adc-hi8435 | 22 The low voltage threshold range is between 2..21V.
23 Hysteresis between low and high thresholds can not be lower then 2 and
39 The high voltage threshold range is between 3..22V.
40 Hysteresis between low and high thresholds can not be lower then 2 and
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | percpu-refcount.h | 10 * 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 …]
|
| D | dim.h | 14 * 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).
|
| /kernel/linux/linux-5.10/drivers/clk/zynqmp/ |
| D | pll.c | 15 * @hw: Handle between common and hardware-specific interfaces
44 * @hw: Handle between common and hardware-specific interfaces
66 * @hw: Handle between common and hardware-specific interfaces
92 * @hw: Handle between common and hardware-specific interfaces
126 * @hw: Handle between common and hardware-specific interfaces
160 * @hw: Handle between common and hardware-specific interfaces
212 * @hw: Handle between common and hardware-specific interfaces
236 * @hw: Handle between common and hardware-specific interfaces
266 * @hw: Handle between common and hardware-specific interfaces
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-bus-iio-adc-hi8435 | 23 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
|
| D | sysfs-class-backlight-adp5520 | 17 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.
|
| D | sysfs-class-backlight-adp8860 | 22 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.
|
| /kernel/linux/linux-4.19/Documentation/driver-api/ |
| D | device_connection.rst | 15 Device connections are generic descriptions of any type of connection between
18 Device connections alone do not create a dependency between the two devices.
20 A dependency between the two devices exists only if one of the two endpoint
34 is needed if there are multiple connections between the two devices.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/memory-controllers/ |
| D | ti-aemif.txt | 96 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
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/memory-controllers/ |
| D | ti-aemif.txt | 96 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
|
| /kernel/linux/linux-5.10/drivers/dma-buf/ |
| D | Kconfig | 11 userspace via Sync File fds for synchronization between drivers via
43 bool "Move notify between drivers (EXPERIMENTAL)"
52 execution context and memory management between drivers.
66 between drivers.
|
| /kernel/linux/linux-4.19/Documentation/media/uapi/v4l/ |
| D | field-order.rst | 9 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
83 also indicate this order when it cannot distinguish between
122 any dropped fields between them (fields can drop individually),
|
| /kernel/linux/linux-5.10/drivers/staging/media/atomisp/pci/isp/kernels/tnr/tnr_1.0/ |
| D | ia_css_tnr_types.h | 25 * 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
|
| /kernel/linux/linux-5.10/Documentation/input/ |
| D | multi-touch-protocol.rst | 53 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 …]
|
| /kernel/linux/linux-4.19/Documentation/input/ |
| D | multi-touch-protocol.rst | 53 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 …]
|
| /kernel/linux/linux-5.10/drivers/clk/zynq/ |
| D | pll.c | 16 * @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
|