Searched full:tuple (Results 1 – 25 of 49) sorted by relevance
12
| /Documentation/devicetree/bindings/phy/ |
| D | apm-xgene-phy.txt | 19 Two set of 3-tuple setting for each (up to 3)
25 Two set of 3-tuple setting for each (up to 3)
28 gain control. Two set of 3-tuple setting for each
31 - apm,tx-amplitude : Amplitude control. Two set of 3-tuple setting for
36 3-tuple setting for each (up to 3) supported link
40 3-tuple setting for each (up to 3) supported link
44 3-tuple setting for Gen1, Gen2, and Gen3. Range is
46 - apm,tx-speed : Tx operating speed. One set of 3-tuple for each
49 1 = 2-4Gbps (1st tuple default)
51 3 = 8-15Gbps (2nd tuple default)
[all …]
|
| /Documentation/devicetree/bindings/gpio/ |
| D | airoha,en7523-gpio.yaml | 26 The first tuple points to the input register.
27 The second and third tuple point to the direction registers
28 The fourth tuple points to the output register
|
| /Documentation/driver-api/early-userspace/ |
| D | buffer-format.rst | 95 tuple is looked up in a tuple buffer. If not found, it is entered in
96 the tuple buffer and the entry is created as usual; if found, a hard
108 When a "TRAILER!!!" end-of-archive marker is seen, the tuple buffer is
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-trigger-pattern.txt | 9 the tuple with duration less than dimming interval (50ms) is treated as a step
32 use zero-time lengths (the brightness must be same as the previous tuple's). So
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | arm,mhuv2.yaml | 92 present as an array of tuples, where each tuple describes details about
96 The first field of a tuple signifies the transfer protocol, 0 is reserved
98 Using any other value in the first field of a tuple makes it invalid.
100 The second field of a tuple signifies the number of channel windows where
|
| /Documentation/devicetree/bindings/arm/keystone/ |
| D | ti,k3-sci-common.yaml | 39 description: Should contain a single tuple of <proc_id host_id>.
|
| /Documentation/networking/ |
| D | tls-offload.rst | 98 to retrieve the connection 5-tuple and socket family (IPv4 vs IPv6).
163 a connection identifier (note that a 5-tuple lookup is insufficient to identify
175 checksum and performs a 5-tuple lookup to find any TLS connection the packet
176 may belong to (technically a 4-tuple
473 5-tuple matching limitations
476 The device can only recognize received packets based on the 5-tuple
481 any intermediate software device, therefore a 5-tuple match may
|
| D | scaling.rst | 39 and/or transport layer headers-- for example, a 4-tuple hash over
64 can be directed to their own receive queue. Such “n-tuple” filters can
154 To make use of the new context direct traffic to it using an n-tuple
188 flow hash over the packet’s addresses or ports (2-tuple or 4-tuple hash
|
| /Documentation/devicetree/bindings/misc/ |
| D | atmel-ssc.txt | 9 - clock-names: tuple listing input clock names.
|
| /Documentation/devicetree/bindings/mtd/ |
| D | cadence-nand-controller.txt | 5 - reg : Contains two entries, each of which is a tuple consisting of a
|
| /Documentation/filesystems/ |
| D | path-lookup.txt | 44 the namespace. A path is represented as a (dentry, vfsmount) tuple. The name
79 In order to lookup a dcache (parent, name) tuple, we take a hash on the tuple
82 against our (parent, name) tuple.
302 so we can load this tuple atomically, and also check whether any of its
304 * Dentry lookups (based on parent, candidate string tuple) recheck the parent
|
| /Documentation/devicetree/bindings/mmc/ |
| D | atmel-hsmci.txt | 16 - clock-names: tuple listing input clock names.
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | net_prio.rst | 37 file can be modified by echoing a string into the file using the same tuple
|
| /Documentation/pcmcia/ |
| D | driver-changes.rst | 62 * New CIS tuple access (as of 2.6.33)
65 only interested in one (raw) tuple, or "pcmcia_loop_tuple()" if it is
|
| /Documentation/devicetree/bindings/opp/ |
| D | ti,omap-opp-supply.yaml | 53 description: An array of u32 tuple items providing information about
|
| /Documentation/driver-api/media/ |
| D | v4l2-event.rst | 12 identified by the ``(type, id)`` tuple.
26 So every ``(type, ID)`` event tuple will have its own
|
| /Documentation/netlink/specs/ |
| D | ovs_flow.yaml | 234 name: ovs-key-ct-tuple-ipv4
572 name: ct-orig-tuple-ipv4
574 struct: ovs-key-ct-tuple-ipv4
576 name: ct-orig-tuple-ipv6
|
| /Documentation/trace/postprocess/ |
| D | trace-pagealloc-postprocess.pl | 113 my $tuple;
114 foreach $tuple (split /\s/, $regex) {
115 my ($key, $value) = split(/=/, $tuple);
|
| /Documentation/ABI/stable/ |
| D | sysfs-bus-firewire | 35 Specifier_id and version within each tuple are separated
|
| /Documentation/devicetree/bindings/net/dsa/ |
| D | vitesse,vsc73xx.yaml | 75 # bus, the if-clause will fail if reg is a tuple such as for a
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | pamu.txt | 21 Interrupt mappings. The first tuple is the normal PAMU
|
| /Documentation/networking/device_drivers/ethernet/aquantia/ |
| D | atlantic.rst | 263 3. 8 L3/L4 5-Tuple rules
281 - Locations 32 - 39 for L3/L4 5-tuple filters (locations 32, 36 for IPv6)
283 The L3/L4 5-tuple (protocol, source and destination IP address, source and
|
| /Documentation/devicetree/bindings/soc/fsl/cpm_qe/ |
| D | fsl,cpm1-tsa.yaml | 119 A list of tuple that indicates the Tx or Rx time-slots routes.
|
| D | fsl,qe-tsa.yaml | 124 A list of tuple that indicates the Tx or Rx time-slots routes.
|
| /Documentation/sphinx/ |
| D | rstFlatTable.py | 148 if isinstance(colwidths, tuple):
150 # colwidths) tuple, where widths is a string (i.e. 'auto').
|
12