Searched full:aligned (Results 1 – 25 of 184) sorted by relevance
12345678
| /Documentation/driver-api/dmaengine/ |
| D | pxa_dma.rst | 100 - if Buffer1 and Buffer2 had all their addresses 8 bytes aligned
102 - and if Buffer3 has at least one address not 4 bytes aligned
107 this specific case if the DMA is already running in aligned mode.
146 - a driver submitted an aligned tx1, not chained
148 - a driver submitted an aligned tx2 => tx2 is cold chained to tx1
150 - a driver issued tx1+tx2 => channel is running in aligned mode
152 - a driver submitted an aligned tx3 => tx3 is hot-chained
159 - a driver submitted an aligned tx5 => tx5 is put in submitted queue, not
162 - a driver submitted an aligned tx6 => tx6 is put in submitted queue,
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-platform-docg3 | 8 which can cover any part of it, block aligned, called DPS.
25 which can cover any part of it, block aligned, called DPS.
|
| D | sysfs-bus-iio-mpu6050 | 13 aligned with each other. All axes are exactly the same.
|
| /Documentation/filesystems/ |
| D | erofs.rst | 131 fsoffset=%llu Specify block-aligned filesystem offset for the primary device.
150 |-> aligned with the block size
156 All data areas should be aligned with the block size, but metadata areas
161 Each valid inode should be aligned with an inode slot, which is a fixed
169 |-> aligned with 8B
175 |-> aligned with the inode slot size
182 .____________________________________________________|-> aligned with 4B
192 |-> aligned with 4B
193 |-> aligned with 4B
234 |-> aligned by 4 bytes
[all …]
|
| /Documentation/devicetree/bindings/fsi/ |
| D | fsi-master-ast-cf.txt | 17 the ColdFire. Must be 2M aligned on
18 AST2400 and 1M aligned on AST2500
|
| /Documentation/devicetree/bindings/mmc/ |
| D | synopsys-dw-mshc-common.yaml | 51 fifo-watermark-aligned:
54 watermark in PIO mode. But fifo watermark is requested to be aligned
|
| /Documentation/virt/kvm/devices/ |
| D | mpic.rst | 22 naturally aligned. A value of zero disables the mapping.
28 must be 4-byte aligned.
|
| D | arm-vgic.rst | 29 This address needs to be 4K aligned and the region covers 4 KByte.
34 This address needs to be 4K aligned and the region covers 8 KByte.
40 -EINVAL Incorrectly aligned address
67 confirm its expected behavior is aligned with the KVM implementation.
|
| D | arm-vgic-its.rst | 28 This address needs to be 64K aligned and the region covers 128K.
34 -EINVAL Incorrectly aligned address
122 -EINVAL Offset is not 64-bit aligned
168 - ITT_addr matches bits [51:8] of the ITT address (256 Byte aligned).
|
| /Documentation/core-api/ |
| D | unaligned-memory-access.rst | 103 to pad structures so that accesses to fields are suitably aligned (assuming
107 parameters to a naturally aligned scheme, based on the size of the type of
177 16-bit-aligned addresses. It is up to the caller to ensure this alignment or
235 aligned memory, using these macros to access unaligned memory can be costly in
246 On architectures that require aligned loads, networking requires that the IP
247 header is aligned on a four-byte boundary to optimise the IP stack. For
257 required to copy the incoming frame into an aligned buffer. Because this is
|
| /Documentation/arch/sparc/oradax/ |
| D | dax-hv-api.txt | 352 0x0 Byte aligned, 1 byte elements
353 0x1 Byte aligned, 2 byte elements
354 0x2 Byte aligned, 4 byte elements
355 0x3 Byte aligned, 8 byte elements
356 0x4 16 byte aligned, 16 byte elements
405 …The only supported output format is a padded, byte-aligned output stream, using output codes 0x0 -…
584 … 0 Huffman encoding. Must use 64 byte aligned table
586 … 1 OZIP encoding. Must use 16 byte aligned table
687 than 4 bytes, the value is left-aligned to the lowest address bytes.
689 is less than 4 bytes, the value is left-aligned to the lowest address bytes.
[all …]
|
| /Documentation/cdrom/ |
| D | packet-writing.rst | 59 host to perform aligned writes at 32KB boundaries. Other drives do
61 writes are not 32KB aligned.
64 generates aligned writes::
|
| /Documentation/arch/mips/ |
| D | booting.rst | 21 aligned on a 64 bit boundary.
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | google,open-dice.yaml | 26 description: page-aligned region of memory containing DICE data
|
| /Documentation/devicetree/bindings/rng/ |
| D | timeriomem_rng.yaml | 33 wide and 32-bit aligned.
|
| /Documentation/devicetree/bindings/net/ |
| D | smsc,lan91c111.yaml | 41 32 bits aligned
|
| /Documentation/iio/ |
| D | iio_devbuf.rst | 123 aligned, so the userspace application has to handle the buffers accordingly.
131 If all channels are enabled, the data will be aligned in the buffer as follows::
138 If only channel0 and channel3 are enabled, the data will be aligned in the
|
| /Documentation/bpf/ |
| D | map_array.rst | 18 stored can be of any size, however, all array elements are aligned to 8
22 setting the flag ``BPF_F_MMAPABLE``. The map definition is page-aligned and
23 starts on the first page. Sufficient page-sized and page-aligned blocks of
|
| /Documentation/ABI/stable/ |
| D | sysfs-class-ubi | 149 this volume has to be aligned on. For example, 2048 means that
152 size aligned to the alignment value.
220 eraseblock size of the device aligned on the volume alignment
|
| /Documentation/arch/arm64/ |
| D | booting.rst | 120 2MB aligned base should be as close as possible
124 2MB aligned base such that all image_size bytes
135 The Image must be placed text_offset bytes from a 2MB aligned base
137 between the 2 MB aligned base address and the start of the image has no
146 entirely within a 1 GB aligned physical memory window of up to 32 GB in
456 naturally-aligned 64-bit zero-initalised memory location.
|
| /Documentation/gpu/rfc/ |
| D | i915_vm_bind.h | 96 * The @start, @offset and @length must be 4K page aligned. However the DG2 has
99 * @length must be 64K aligned. Also, UMDs should not mix the local memory 64K
103 * properly aligned. In version 1 (See I915_PARAM_VM_BIND_VERSION), error code
|
| /Documentation/userspace-api/ |
| D | mseal.rst | 35 - The start address must be page aligned.
39 The ``len`` will be paged aligned implicitly by the kernel.
47 * The start address (``addr``) is not page aligned.
|
| /Documentation/w1/slaves/ |
| D | w1_ds28e04.rst | 32 fully aligned blocks of 32 bytes with valid CRC16 values (in bytes 30
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | brcm,bcm947xx-cfe-partitions.yaml | 17 block aligned which is important for determinig a size.
|
| /Documentation/virt/kvm/ |
| D | review-checklist.rst | 33 (all variables and sizes naturally aligned on 64-bit; use specific types
|
12345678