Searched full:length (Results 1 – 25 of 1236) sorted by relevance
12345678910>>...50
| /Documentation/arm64/ |
| D | sve.rst | 23 * SVE registers Z0..Z31, P0..P15 and FFR and the current vector length VL, are
74 2. Vector length terminology
77 The size of an SVE vector (Z) register is referred to as the "vector length".
79 To avoid confusion about the units used to express vector length, the kernel
82 * Vector length (VL) = size of a Z-register in bytes
110 length, the state of the PR_SVE_VL_INHERIT flag, and the deferred vector
111 length (if any), is preserved across all syscalls, subject to the specific
130 the thread's vector length (in sve_context.vl).
169 * The vector length cannot be changed via signal return. If sve_context.vl in
170 the signal frame does not match the current vector length, the signal return
[all …]
|
| /Documentation/staging/ |
| D | lzo.rst | 27 - a length (number of bytes to copy from dictionary)
32 extra data can be a complement for the operand (eg: a length or a distance
41 length, up to 255 may be added in increments by consuming more bytes with a
43 around 255:1). The variable length encoding using #bits is always the same::
45 length = byte & ((1 << #bits) - 1)
46 if (!length) {
47 length = ((1 << #bits) - 1)
48 length += 255*(number of zero bytes)
49 length += first-non-zero-byte
51 length += constant (generally 2 or 3)
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-queue-length.rst | 2 dm-queue-length
5 dm-queue-length is a path selector module for device-mapper targets,
7 The path selector name is 'queue-length'.
30 dm-queue-length increments/decrements 'in-flight' when an I/O is
32 dm-queue-length selects a path with the minimum 'in-flight'.
41 # echo "0 10 multipath 0 0 1 1 queue-length 0 2 1 8:0 128 8:16 128" \
45 test: 0 10 multipath 0 0 1 1 queue-length 0 2 1 8:0 128 8:16 128
|
| /Documentation/devicetree/bindings/phy/ |
| D | qcom,qmp-usb3-dp-phy.yaml | 22 - description: Address and length of PHY's USB serdes block.
23 - description: Address and length of the DP_COM control block.
24 - description: Address and length of PHY's DP serdes block.
89 - description: Address and length of TX.
90 - description: Address and length of RX.
91 - description: Address and length of PCS.
92 - description: Address and length of TX2.
93 - description: Address and length of RX2.
94 - description: Address and length of pcs_misc.
129 - description: Address and length of TX.
[all …]
|
| /Documentation/devicetree/bindings/powerpc/nintendo/ |
| D | wii.txt | 31 - reg : should contain the VI registers location and length
42 - reg : should contain the PI registers location and length
64 - reg : should contain the DSP registers location and length
76 - reg : should contain the SI registers location and length
87 - reg : should contain the AI registers location and length
97 - reg : should contain the EXI registers location and length
107 - reg : should contain the OHCI registers location and length
117 - reg : should contain the EHCI registers location and length
127 - reg : should contain the SDHCI registers location and length
136 - reg : should contain the IPC registers location and length
[all …]
|
| D | gamecube.txt | 22 - reg : should contain the VI registers location and length
33 - reg : should contain the PI registers location and length
53 - reg : should contain the DSP registers location and length
65 - reg : should contain the ARAM start (zero-based) and length
74 - reg : should contain the DI registers location and length
85 - reg : should contain the AI registers location and length
97 - reg : should contain the SI registers location and length
107 - reg : should contain the EXI registers location and length
|
| /Documentation/userspace-api/media/v4l/ |
| D | func-munmap.rst | 23 .. c:function:: int munmap( void *start, size_t length )
32 ``length``
33 Length of the mapped buffer. This must be the same value as given to
35 :c:type:`v4l2_buffer` ``length`` field for the
37 :c:type:`v4l2_plane` ``length`` field for the
53 The ``start`` or ``length`` is incorrect, or no buffers have been
|
| D | func-mmap.rst | 23 .. c:function:: void *mmap( void *start, size_t length, int prot, int flags, int fd, off_t offset )
35 ``length``
36 Length of the memory area to map. This must be the same value as
38 :c:type:`v4l2_buffer` ``length`` field for the
40 the struct :c:type:`v4l2_plane` ``length`` field for
101 The :c:func:`mmap()` function asks to map ``length`` bytes starting at
106 Suitable length and offset parameters are queried with the
127 The ``start`` or ``length`` or ``offset`` are not suitable. (E. g.
|
| D | mmap.rst | 42 API case, the ``m.offset`` and ``length`` returned in a struct
47 containing its own ``m.offset`` and ``length``. When using the
51 offset and length values must not be modified. Remember, the buffers are
64 size_t length;
106 buffers[i].length = buffer.length; /* remember for munmap() */
108 buffers[i].start = mmap(NULL, buffer.length,
124 munmap(buffers[i].start, buffers[i].length);
137 size_t length[FMT_NUM_PLANES];
174 /* length in struct v4l2_buffer in multi-planar API stores the size
176 buffer.length = FMT_NUM_PLANES;
[all …]
|
| /Documentation/netlabel/ |
| D | draft-ietf-cipso-ipsecurity-01.txt | 74 Option length: Variable
96 LENGTH INTERPRETATION
104 This field is 1 octet in length. Its value is 134.
107 3.2 Length
109 This field is 1 octet in length. It is the total length of the option
110 including the type and length fields. With the current IP header length
147 a tag type identifier followed by the length of the tag and ends with the
175 TYPE LENGTH INFORMATION
179 In the three tag types described in this document, the length and count
181 IP options. If the IP header is later expanded, then the length and count
[all …]
|
| /Documentation/devicetree/bindings/net/wireless/ |
| D | marvell-8xxx.txt | 23 corresponding array length:
24 "marvell,caldata-txpwrlimit-2g" (length = 566).
25 "marvell,caldata-txpwrlimit-5g-sub0" (length = 502).
26 "marvell,caldata-txpwrlimit-5g-sub1" (length = 688).
27 "marvell,caldata-txpwrlimit-5g-sub2" (length = 750).
28 "marvell,caldata-txpwrlimit-5g-sub3" (length = 502).
44 The calibration data is an array of unsigned values, the length
|
| /Documentation/networking/ |
| D | udplite.rst | 9 is a variable-length checksum. This has advantages for transport of multimedia
38 length (default = header length = 8). Details are in the next section.
61 single socket option, which takes an integer specifying the coverage length:
70 sets the checksum coverage length to 20 bytes (12b data + 8b header).
123 If the sender specifies a value of 0 as coverage length, the module
124 assumes full coverage, transmits a packet with coverage length of 0
127 if the specified coverage length exceeds the packet length, the packet
128 length is used instead as coverage length.
132 The receiver specifies the minimum value of the coverage length it
176 The send buffer size has implications on the checksum coverage length.
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | brcm,amac.txt | 8 - reg: Address and length of the register set for the device. It
12 "amac_base": Address and length of the GMAC registers
13 "idm_base": Address and length of the GMAC IDM registers
15 "nicpm_base": Address and length of the NIC Port Manager
|
| /Documentation/devicetree/bindings/arm/ |
| D | atmel-sysregs.txt | 5 - reg : Should contain registers location and length
9 - reg: Should contain registers location and length
15 - reg: Should contain registers location and length
21 - reg: Should contain registers location and length
32 - reg: Should contain registers location and length
49 - reg: Should contain registers location and length
63 - reg: Should contain registers location and length
95 - reg: should contain registers location and length
162 - reg: Should contain registers location and length
181 - reg: Should contain registers location and length
|
| /Documentation/scsi/ |
| D | arcmsr_spec.rst | 51 1st uint32_t Data length (1--124)
194 variable length of data including length,
198 variable length of data
204 command block length (low byte)
207 command block length (high byte)
209 .. Note:: command block length shouldn't > 2040 bytes,
210 length excludes these two bytes
216 variable length data bytes
287 byte 0,1 length
289 byte 3 password length (should be 0x0f)
[all …]
|
| /Documentation/userspace-api/media/dvb/ |
| D | dmx-mmap.rst | 25 .. c:function:: void *mmap( void *start, size_t length, int prot, int flags, int fd, off_t offset )
37 ``length``
38 Length of the memory area to map. This must be a multiple of the
39 DVB packet length (188, on most drivers).
80 The :c:func:`mmap()` function asks to map ``length`` bytes starting at
85 Suitable length and offset parameters are queried with the
105 The ``start`` or ``length`` or ``offset`` are not suitable. (E. g.
|
| D | dmx-munmap.rst | 25 .. c:function:: int munmap( void *start, size_t length )
34 ``length``
35 Length of the mapped buffer. This must be the same value as given to
51 The ``start`` or ``length`` is incorrect, or no buffers have been
|
| /Documentation/devicetree/bindings/display/ti/ |
| D | ti,omap2-dss.txt | 12 - reg: address and length of the register space
27 - reg: address and length of the register space
41 - reg: address and length of the register space
50 - reg: address and length of the register space
|
| D | ti,omap3-dss.txt | 12 - reg: address and length of the register space
34 - reg: address and length of the register space
50 - reg: address and length of the register space
61 - reg: address and length of the register space
|
| /Documentation/devicetree/bindings/iommu/ |
| D | nvidia,tegra30-smmu.txt | 5 - reg : Should contain 3 register banks(address and length) for each
9 - dma-window : IOVA start address and length.
19 dma-window = <0 0x40000000>; /* IOVA start & length */
|
| /Documentation/devicetree/bindings/powerpc/ |
| D | ibm,vas.txt | 11 window context start and length, OS/User window context start and length,
12 "Paste address" start and length, "Paste window id" start bit and number
|
| /Documentation/devicetree/bindings/pwm/ |
| D | pxa-pwm.txt | 9 - reg: Physical base address and length of the registers used by the PWM channel
11 length covers only the register window for one PWM output, not that of the
12 entire PWM controller. Currently length is 0x10 for all supported devices.
|
| /Documentation/usb/ |
| D | usbmon.rst | 166 in this word, they proceed to read Data Length (except for isochronous URBs).
168 reading the Data Length or isochronous descriptors.
179 status, offset, and length respectively. For submissions, initial length
180 is reported. For callbacks, actual length is reported.
182 - Data Length. For submissions, this is the requested length. For callbacks,
183 this is the actual length.
185 - Data tag. The usbmon may not always capture data, even if length is nonzero.
191 The length of collected data is limited and can be less than the data length
192 reported in the Data Length word. In the case of an Isochronous input (Zi)
193 completion where the received data is sparse in the buffer, the length of
[all …]
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | brcm,dpfe-cpu.txt | 14 - start address and length of the DCPU register space
15 - start address and length of the DCPU data memory space
16 - start address and length of the DCPU instruction memory space
|
| /Documentation/devicetree/bindings/firmware/ |
| D | nvidia,tegra210-bpmp.txt | 16 - reg: physical base address and length for HW synchornization primitives
17 1) base address and length to Tegra 'atomics' hardware
18 2) base address and length to Tegra 'semaphore' hardware
|
12345678910>>...50