between (full) in projects: linux - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

12 3 4 5 6 7 8 9 10 >>...131

/linux/tools/testing/selftests/net/forwarding/
H A 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"
/linux/net/dccp/ccids/lib/
H A D	packet_history.c
/linux/include/linux/
H A 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. 273 * This function is safe to call as long as @ref is between init and exit. 304 * This function is safe to call as long as @ref is between init and exit. 324 * This function is safe to call as long as @ref is between init and exit. [all …]
/linux/Documentation/userspace-api/
H A D	dma-buf-alloc-exchange.rst	9 support for sharing pixel-buffer allocations between processes, devices, and 10 subsystems. Modern systems require extensive integration between all three 80 A value that denotes the relationship between pixel-location co-ordinates 81 and byte-offset values. Typically used as the byte offset between two 83 layouts, the byte offset between two vertically-adjacent pixels. For 101 Each ``DRM_FORMAT_*`` token describes the translation between a pixel 105 and their locations within the pixel memory, and the relationship between color 120 Format modifiers describe a translation mechanism between these per-pixel memory 169 between two contiguous row. For example, a ``DRM_FORMAT_MOD_LINEAR`` buffer 222 CPU access routines to copy data between the different uses, with the [all …]
/linux/include/linux/sched/
H A D	sd_flags.h	`40 * 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. 99 * NEEDS_GROUPS: Per-CPU capacity is asymmetric between groups. 108 * NEEDS_GROUPS: Capacity is shared between groups. 115 * NEEDS_GROUPS: Clusters are shared between groups. 124 * NEEDS_GROUPS: Caches are shared between groups.`
/linux/drivers/clk/zynqmp/
H A D	pll.c	15 * @hw: Handle between common and hardware-specific interfaces 45 * @hw: Handle between common and hardware-specific interfaces 69 * @hw: Handle between common and hardware-specific interfaces 95 * @hw: Handle between common and hardware-specific interfaces 128 * @hw: Handle between common and hardware-specific interfaces 169 * @hw: Handle between common and hardware-specific interfaces 221 * @hw: Handle between common and hardware-specific interfaces 245 * @hw: Handle between common and hardware-specific interfaces 275 * @hw: Handle between common and hardware-specific interfaces
/linux/Documentation/devicetree/bindings/memory-controllers/
H A 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`
/linux/Documentation/devicetree/bindings/spi/
H A D	cdns,qspi-nor-peripheral-props.yaml	`25 outputs are de-asserted between transactions. 29 Delay in nanoseconds between one chip select being de-activated 34 Delay in nanoseconds between last bit of current transaction and 39 Delay in nanoseconds between setting qspi_n_ss_out low and`
/linux/Documentation/dev-tools/
H A D	checkuapi.rst	78 Checking changes to UAPI headers between HEAD and dirty tree... 102 Checking changes to UAPI headers between HEAD and dirty tree... 126 Checking changes to UAPI headers between HEAD and dirty tree... 152 Checking changes to UAPI headers between HEAD and dirty tree... 177 Checking changes to UAPI headers between HEAD^1 and HEAD... 184 let's pass ``-p HEAD~2`` to the script so it checks UAPI changes between 190 Checking changes to UAPI headers between HEAD~2 and HEAD... 229 No changes to UAPI headers were applied between HEAD and dirty tree 240 Checking changes to UAPI headers between HEAD and dirty tree... 287 Checking changes to UAPI headers between HEAD and dirty tree... [all …]
/linux/drivers/net/ethernet/freescale/
H A D	ucc_geth.h	64 frames) transmitted that were between 68 frames) transmitted that were between 128 74 frames) received that were between MINLength 77 frames) received that were between 128 498 u32 txpkts256; /* total packets (including bad) between 256 500 u32 txpkts512; /* total packets (including bad) between 512 502 u32 txpkts1024; /* total packets (including bad) between 1024 504 u32 txpktsjumbo; /* total packets (including bad) between 1024 522 u32 pkts256; /* total frames (including bad) between 256 and 524 u32 pkts512; /* total frames (including bad) between 512 and [all …]
/linux/drivers/accel/habanalabs/common/
H A D	security.c	`298 * @dcore_offset: offset between dcores 300 * @instance_offset: offset between instances 350 * @dcore_offset: offset between dcores 352 * @instance_offset: offset between instances 378 * @dcore_offset: offset between dcores 380 * @instance_offset: offset between instances 436 * @dcore_offset: offset between dcores 438 * @instance_offset: offset between instances 464 * @instance_offset: offset between instances 512 * @instance_offset: offset between instances [all …]`
H A D	security.h	`32 * @major_offset: address gap between 2 consecutive major blocks of particular type, 33 * e.g., offset between NIC0_UMR0_0 and NIC1_UMR0_0 is 0x80000. 34 * @minor_offset: address gap between 2 consecutive minor blocks of particular type, 35 * e.g., offset between NIC0_UMR0_0 and NIC0_UMR1_0 is 0x20000. 36 * @sub_minor_offset: address gap between 2 consecutive sub_minor blocks of particular 37 * type, e.g., offset between NIC0_UMR0_0 and NIC0_UMR0_1 is 0x1000.`
/linux/Documentation/input/
H A 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. 268 The distance, in surface units, between the contact and the surface. Zero 289 support is possible if the device can distinguish between the two axes, but 290 not (uniquely) any values in between. In such cases, the range of 301 the device cannot distinguish between the intended touch point and the 306 device cannot distinguish between the intended touch point and the tool 316 between different tool types, such as a finger or a pen. In such cases, the 356 the device can distinguish between a finger along the Y axis (0) and a [all …]
/linux/Documentation/ABI/testing/
H A 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`
/linux/drivers/net/ethernet/atheros/atl1e/
H A D	atl1e.h	259 …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/drivers/clk/zynq/
H A 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`
/linux/tools/memory-model/litmus-tests/
H A D	README	`25 between each pairs of reads. In other words, is smp_mb() 33 between each pairs of reads. In other words, is anything at all 67 Does a unlock+lock pair provides ordering guarantee between a 98 Does a unlock+lock pair provides ordering guarantee between a 102 Does a smp_wmb() (between the stores) and an smp_rmb() (between 213 interleaving descriptions of the relation between a pair of consecutive 254 The descriptors that describe connections between consecutive accesses`
/linux/Documentation/userspace-api/media/v4l/
H A 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 127 any dropped fields between them (fields can drop individually),`
/linux/drivers/net/ethernet/atheros/atl1c/
H A D	atl1c.h	310 …unsigned long rx_sz_65_127; /* The number of good and bad packets received that are between 65 and… 311 …unsigned long rx_sz_128_255; /* The number of good and bad packets received that are between 128 a… 312 …unsigned long rx_sz_256_511; /* The number of good and bad packets received that are between 256 a… 313 …unsigned long rx_sz_512_1023; /* The number of good and bad packets received that are between 512 … 314 …unsigned long rx_sz_1024_1518; /* The number of good and bad packets received that are between 102… 315 …unsigned long rx_sz_1519_max; /* The number of good and bad packets received that are between 1519… 334 …unsigned long tx_sz_65_127; /* The number of good and bad packets transmitted that are between 65 … 335 …unsigned long tx_sz_128_255; /* The number of good and bad packets transmitted that are between 12… 336 …unsigned long tx_sz_256_511; /* The number of good and bad packets transmitted that are between 25… 337 …unsigned long tx_sz_512_1023; /* The number of good and bad packets transmitted that are between 5… [all …]
/linux/arch/arm/mach-omap2/
H A D	clockdomain.h	`77 * struct clkdm_dep - encode dependencies between clockdomains 147 * @clkdm_add_wkdep: Add a wakeup dependency between clk domains 148 * @clkdm_del_wkdep: Delete a wakeup dependency between clk domains 149 * @clkdm_read_wkdep: Read wakeup dependency state between clk domains 151 * @clkdm_add_sleepdep: Add a sleep dependency between clk domains 152 * @clkdm_del_sleepdep: Delete a sleep dependency between clk domains 153 * @clkdm_read_sleepdep: Read sleep dependency state between clk domains`
/linux/tools/perf/pmu-events/arch/x86/jaketown/
H A D	uncore-memory.json	184 …be used to track multiple ranks simultaneously. There is no distinction between the different CKE… 194 …be used to track multiple ranks simultaneously. There is no distinction between the different CKE… 204 …be used to track multiple ranks simultaneously. There is no distinction between the different CKE… 214 …be used to track multiple ranks simultaneously. There is no distinction between the different CKE… 224 …be used to track multiple ranks simultaneously. There is no distinction between the different CKE… 234 …be used to track multiple ranks simultaneously. There is no distinction between the different CKE… 244 …be used to track multiple ranks simultaneously. There is no distinction between the different CKE… 254 …be used to track multiple ranks simultaneously. There is no distinction between the different CKE… 282 …constraints or by the PCU throttling. It is not possible to distinguish between the two. This ca… 292 …constraints or by the PCU throttling. It is not possible to distinguish between the two. This ca… [all …]
/linux/Documentation/devicetree/bindings/arm/
H A D	arm,coresight-cti.yaml	17 The CTI component properties define the connections between the individual 30 In general the connections between CTI and components via the trigger signals 35 between CTI and the CPU core and ETM if present. In the case of a v8 44 on the connections between the CTI and other components for correct operation. 48 between CTI and other CoreSight components. 50 Certain triggers between CoreSight devices and the CTI have specific types 106 propagated between sockets. 134 between this CTI and another hardware device. This device may be a CPU,
/linux/Documentation/devicetree/bindings/iio/frequency/
H A D	adi,admfm2000.yaml	`46 Enable mixer mode for the channel. It downconverts RF between 5 GHz 47 and 32 GHz to IF between 0.5 GHz and 8 GHz. If not present, the channel 49 between 2 GHz and 8 GHz to IF between 0.5 GHz and 8 GHz.`
/linux/Documentation/driver-api/
H A D	interconnect.rst	`12 latency and priority between multiple interconnected devices or functional 18 An example of interconnect buses are the interconnects between various 68 Interconnect path is everything between two endpoints including all the nodes 91 get paths between endpoints and set their bandwidth/latency/QoS requirements 100 software shouldn't rely on format details change between kernel versions. 129 # Get path between src_node and dst_node. This is only`
/linux/Documentation/devicetree/bindings/input/touchscreen/
H A D	fsl-mx25-tcq.txt	`16 between 1 and 4096. It is the ratio between the internal reference voltage 17 and the measured voltage after the plate was precharged. Resistance between`

12 3 4 5 6 7 8 9 10 >>...131