Searched full:tuple (Results 1 – 25 of 59) sorted by relevance
123
| /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 …]
|
| D | phy-hi3798cv200-combphy.txt | 21 peripheral controller, as a 3 integers tuple:
|
| /Documentation/devicetree/bindings/c6x/ |
| D | dscr.txt | 46 a lock register. Each tuple consists of the register offset, lock register
57 is contained in a single byte. This property has two tuples. Each tuple has
65 Each tuple describes a range of identical bitfields used to control one or
66 more devices (one bitfield per device). The layout of each tuple is:
81 for device states controlled by the DSCR. Each tuple describes a range of
83 bitfield per device). The layout of each tuple is:
|
| /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/gpio/ |
| D | gpio-vf610.txt | 11 - reg : The first reg tuple represents the PORT module, the second tuple
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | qcom,pdc.txt | 37 The first element of the tuple is the PDC pin for the
52 The first element of the tuple is the starting PDC port.
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | ti-da8xx-ddrctl.txt | 12 - reg: a tuple containing the base address of the memory
|
| /Documentation/devicetree/bindings/serial/ |
| D | ingenic,uart.txt | 14 - clock-names: tuple listing input clock names.
|
| D | cdns,uart.txt | 11 - clock-names: Tuple to identify input clocks, must contain "uart_clk" and "pclk"
|
| /Documentation/devicetree/bindings/spi/ |
| D | spi_atmel.txt | 9 - clock-names: tuple listing input clock names.
|
| /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
455 5-tuple matching limitations
458 The device can only recognize received packets based on the 5-tuple
463 any intermediate software device, therefore a 5-tuple match may
|
| /Documentation/devicetree/bindings/sound/ |
| D | atmel-classd.txt | 15 Tuple listing input clock names.
|
| /Documentation/devicetree/bindings/misc/ |
| D | atmel-ssc.txt | 9 - clock-names: tuple listing input clock names.
|
| /Documentation/devicetree/bindings/net/can/ |
| D | fsl-flexcan.txt | 13 - interrupts : Interrupt tuple for this device
|
| /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/mfd/ |
| D | atmel-tcb.txt | 10 - clock-names: tuple listing input clock names.
|
| D | qcom,spmi-pmic.txt | 44 - interrupts: Interrupts are specified as a 4-tuple. For more information
|
| /Documentation/devicetree/bindings/mmc/ |
| D | atmel-hsmci.txt | 16 - clock-names: tuple listing input clock names.
|
| D | sdhci-am654.txt | 19 - clock-names: Tuple including "clk_xin" and "clk_ahb"
|
| /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/devicetree/bindings/opp/ |
| D | ti-omap5-opp-supply.txt | 32 - ti,efuse-settings: An array of u32 tuple items providing information about
|
| /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/net/ |
| D | macb.txt | 25 - clock-names: Tuple listing input clock names.
|
| /Documentation/devicetree/bindings/spmi/ |
| D | qcom,spmi-pmic-arb.txt | 38 - #interrupt-cells : must be set to 4. Interrupts are specified as a 4-tuple:
|
123