Searched full:padding (Results 1 – 25 of 102) sorted by relevance
12345
| /Documentation/devicetree/bindings/display/mediatek/ |
| D | mediatek,padding.yaml | 4 $id: http://devicetree.org/schemas/display/mediatek/mediatek,padding.yaml#
7 title: MediaTek Display Padding
14 Padding provides ability to add pixels to width and height of a layer with
17 we need Padding to deal with odd width.
18 Please notice that even if the Padding is in bypass mode, settings in
24 - mediatek,mt8188-disp-padding
25 - mediatek,mt8195-mdp3-padding
35 - description: Padding's clocks
76 padding0: padding@1c11d000 {
77 compatible = "mediatek,mt8188-disp-padding";
|
| /Documentation/networking/device_drivers/cellular/qualcomm/ |
| D | rmnet.rst | 48 Padding is the number of bytes to be appended to the payload to
53 Payload length includes the padding length but does not include MAP header
74 Padding is the number of bytes to be appended to the payload to
79 Payload length includes the padding length but does not include MAP header
98 Padding is the number of bytes to be appended to the payload to
128 Padding is the number of bytes to be appended to the payload to
133 Payload length includes the padding length but does not include MAP header
186 MAP header|IP Packet|Optional padding|MAP header|IP Packet|Optional padding....
188 MAP header|IP Packet|Optional padding|MAP header|Command Packet|Optional pad...
|
| /Documentation/filesystems/ext4/ |
| D | verity.rst | 14 - Zero-padding to the next 65536-byte boundary. This padding need not
23 - Zero-padding to the next filesystem block boundary.
29 - Zero-padding to the next offset that is 4 bytes before a filesystem
|
| /Documentation/sphinx-static/ |
| D | theme_overrides.css | 49 padding-top: 1px;
50 padding-bottom: 1px;
53 padding-top: 1px;
54 padding-bottom: 1px;
107 /* inline literal: drop the borderbox, padding and red color */
112 padding: unset;
|
| D | custom.css | 16 div.body { padding: 0 15px 0 10px; }
17 div.sphinxsidebarwrapper { padding: 1em 0.4em; }
101 padding: .5em;
109 padding: 0.5em;
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | partition.yaml | 71 mean that padding is added before the entry. The padding is part of
88 entry itself (the padding is performed only when its parent section is
89 assembled), the end result is that the entry ends with the padding
105 But there may be padding at the end. While this does not affect the
106 content of the entry itself (the padding is performed only when its
108 with the padding bytes, so may grow. If ‘align-end’ is not provided,
|
| /Documentation/userspace-api/media/v4l/ |
| D | metafmt-generic.rst | 56 Data Units, with one padding byte after every four bytes of metadata. This
61 The packing of the data follows the MIPI CSI-2 specification and the padding of
72 Each cell is one byte. "M" denotes a byte of metadata and "x" a byte of padding.
100 Data Units, with one padding byte after every two bytes of metadata. This format
105 The packing of the data follows the MIPI CSI-2 specification and the padding of
116 Each cell is one byte. "M" denotes a byte of metadata and "x" a byte of padding.
146 Data Units, with three padding bytes after every four bytes of metadata. This
151 The packing of the data follows the MIPI CSI-2 specification and the padding of
157 Each cell is one byte. "M" denotes a byte of metadata and "x" a byte of padding.
189 Data Units, with one padding byte after every byte of metadata. This format is
[all …]
|
| D | pixfmt-v4l2.rst | 68 padding bytes at the end of each line. Drivers however may ignore
74 Video hardware may access padding bytes, therefore they must
75 reside in accessible memory. Consider cases where padding bytes
77 Input devices may write padding bytes, the value is undefined.
78 Output devices ignore the contents of padding bytes.
83 planes of a YUV 4:2:0 image have half as many padding bytes
|
| D | vidioc-g-fbuf.rst | 163 Video hardware may access padding bytes, therefore they must
165 padding bytes after the last line of an image cross a system page
166 boundary. Capture devices may write padding bytes, the value is
167 undefined. Output devices ignore the contents of padding bytes.
172 planes of a YUV 4:2:0 image have half as many padding bytes
|
| D | pixfmt-yuv-luma.rst | 19 - `0` denotes padding bits set to 0.
210 padding zeros in the 4 low bits, in contrast to the Y12 format, which has
211 its padding located in the most significant bits of the 16 bit word.
|
| D | v4l2-selection-targets.rst | 74 - The active area and all padding pixels that are inserted or
|
| /Documentation/driver-api/ |
| D | ioctl.rst | 98 user space and the padding is treated correctly.
170 has four bytes of padding between a and b on x86-64, plus another four
171 bytes of padding at the end, but no padding on i386, and it needs a
176 implicit padding. The ``pahole`` tool can be used for checking the
185 implicit padding.
203 implicit padding in data structures. Where there is implicit padding
|
| /Documentation/networking/ |
| D | iso15765-2.rst | 167 * ``CAN_ISOTP_TX_PADDING``: enable padding for transmitted frames, using
168 ``txpad_content`` as value for the padding bytes.
170 * ``CAN_ISOTP_RX_PADDING``: enable padding for the received frames, using
171 ``rxpad_content`` as value for the padding bytes.
173 * ``CAN_ISOTP_CHK_PAD_LEN``: check for correct padding length on the received
176 * ``CAN_ISOTP_CHK_PAD_DATA``: check padding bytes on the received frames
216 * ``txpad_content``: byte used as padding value for transmitted frames.
218 * ``rxpad_content``: byte used as padding value for received frames.
338 -EBADMSG data reception with wrong padding
347 -EBADMSG flow control reception with wrong layout/padding
|
| D | xsk-tx-metadata.rst | 32 | xsk_tx_metadata | padding | payload |
39 xsk_tx_metadata)``. The kernel will ignore the padding (and will still
|
| D | radiotap-headers.rst | 58 padding. So a u16 argument must start on the next u16 boundary if it isn't
77 consisting of two u16s of total length 4. When this happens, the padding
|
| /Documentation/networking/device_drivers/ethernet/freescale/ |
| D | gianfar.rst | 39 Padding chapter
42 The gianfar driver supports padding received frames with 2 bytes
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-net-cdc_ncm | 10 as-is, without any padding, and are terminated with a
13 Padding to tx_max allows the driver to transmit NTBs
20 disable all padding.
149 offsets within the NTB: Padding, shall be transmitted
|
| /Documentation/core-api/ |
| D | swiotlb.rst | 131 Hence there may be pre-padding space that is allocated prior to the start of
133 alloc_align_mask boundary, potentially resulting in post-padding space. Any
134 pre-padding or post-padding space is not initialized by swiotlb code. The
296 Fourth, the io_tlb_slot array keeps track of any "padding slots" allocated to
299 requirements, it may allocate pre-padding space across zero or more slots. But
302 allocation of any padding slots, is not known. The "pad_slots" field records
303 the number of padding slots so that swiotlb_tbl_unmap_single() can free them.
304 The "pad_slots" value is recorded only in the first non-padding slot allocated
|
| D | unaligned-memory-access.rst | 101 above case it would insert 2 bytes of padding in between field1 and field2.
116 where padding would otherwise be inserted, and hence reduce the overall
127 byte of padding at the end of the structure. This padding is added in order
132 insert any padding within structures, useful when you want to use a C struct
142 structure padding is of importance.
|
| /Documentation/filesystems/ |
| D | relay.rst | 43 bytes of it are padding i.e. unused space occurring because a complete
59 The read() interface both removes padding and internally consumes the
97 padding). The read() interface both removes padding and internally
130 padding is automatically removed and will not be seen by
134 descriptor. Sub-buffer padding is automatically removed
410 reserved in each sub-buffer to store the padding count for that
412 subbuf_start() implementation; the padding value for the previous
414 pointer to the previous sub-buffer, since the padding value isn't
|
| /Documentation/process/ |
| D | botching-up-ioctls.rst | 33 * Align everything to the natural size and use explicit padding. 32-bit
35 64-bit platforms do. So we always need padding to the natural size to get
72 * Check all unused fields and flags and all the padding for whether it's 0,
78 structures, even if you never use them in an array - the padding the compiler
|
| /Documentation/admin-guide/ |
| D | bootconfig.rst | 169 padding, size, checksum and 12-byte magic word as below.
171 [initrd][bootconfig][padding][size(le32)][checksum(le32)][#BOOTCONFIG\n]
178 file + padding bytes.
277 the padding null characters.)
|
| /Documentation/devicetree/bindings/reserved-memory/ |
| D | qcom,rmtfs-mem.yaml | 34 memory regions, and that padding around the used portion of the memory
|
| /Documentation/driver-api/early-userspace/ |
| D | buffer-format.rst | 29 ALGN(n) means padding with null bytes to an n-byte boundary
44 formats); arbitrary amounts zero bytes (for padding) can be added
|
| /Documentation/arch/powerpc/ |
| D | cxl.rst | 241 For ABI padding and future extensions
320 For future extensions and padding.
341 For future extensions and padding.
395 For future extensions and padding
|
12345