Lines Matching +full:fixed +full:- +full:layout
39 * further describe the buffer's format - for example tiling or compression.
42 * ----------------
46 * format and data layout of the buffer, and should be the only way to describe
49 * Having multiple fourcc:modifier pairs which describe the same layout should
56 * vendor-namespaced, and as such the relationship between a fourcc code and a
58 * may preserve meaning - such as number of planes - from the fourcc code,
61 * Modifiers must uniquely encode buffer layout. In other words, a buffer must
64 * a modifier: a buffer may match a 64-pixel aligned modifier and a 32-pixel
76 * - Kernel and user-space drivers: for drivers it's important that modifiers
80 * - Higher-level programs interfacing with KMS/GBM/EGL/Vulkan/etc: these users
93 * -----------------------
98 * upstream in-kernel or open source userspace user does not apply.
222 * IEEE 754-2008 binary16 half-precision float
232 * RGBA format with 10-bit components packed in 64-bit per pixel, with 6 bits
248 …010 fourcc_code('V', 'U', '3', '0') /* Y followed by U then V, 10:10:10. Non-linear modifier only …
252 * 16-xx padding occupy lsb
260 * 16-xx padding occupy lsb except Y410
285 * 1-plane YUV 4:2:0
287 * then V), but the exact Linear layout is undefined.
288 * These formats can only be used with a non-Linear modifier.
318 #define DRM_FORMAT_NV24 fourcc_code('N', 'V', '2', '4') /* non-subsampled Cr:Cb plane */
319 #define DRM_FORMAT_NV42 fourcc_code('N', 'V', '4', '2') /* non-subsampled Cb:Cr plane */
362 /* 3 plane non-subsampled (444) YCbCr
370 /* 3 plane non-subsampled (444) YCrCb
395 #define DRM_FORMAT_YUV444 fourcc_code('Y', 'U', '2', '4') /* non-subsampled Cb (1) and Cr (2) plane…
396 #define DRM_FORMAT_YVU444 fourcc_code('Y', 'V', '2', '4') /* non-subsampled Cr (1) and Cb (2) plane…
402 * Format modifiers describe, typically, a re-ordering or modification
406 * The upper 8 bits of the format modifier are a vendor-id as assigned
425 #define DRM_FORMAT_RESERVED ((1ULL << 56) - 1)
439 * When adding a new token please document the layout with a code comment,
445 * DRM_FORMAT_MOD_GENERIC_* definitions are used to provide vendor-neutral names
447 * compatibility, in cases where a vendor-specific definition already exists and
452 * generic layouts (such as pixel re-ordering), which may have
453 * independently-developed support across multiple vendors.
455 * In future cases where a generic layout is identified before merging with a
456 * vendor-specific modifier, a new 'GENERIC' vendor or modifier using vendor
479 * Linear Layout
481 * Just plain linear layout. Note that this is different from no specifying any
483 * which tells the driver to also take driver-internal information into account
492 * implicit, instead it means that the layout is linear. Whether modifiers are
493 * used is out-of-band information carried in an API-specific way (e.g. in a
501 * Intel X-tiling layout
503 * This is a tiled layout using 4Kb tiles (except on gen2 where the tiles 2Kb)
504 * in row-major layout. Within the tile bytes are laid out row-major, with
505 * a platform-dependent stride. On top of that the memory can apply
506 * platform-depending swizzling of some higher address bits into bit6.
508 * Note that this layout is only accurate on intel gen 8+ or valleyview chipsets.
510 * cross-driver sharing. It exists since on a given platform it does uniquely
511 * identify the layout in a simple way for i915-specific userspace, which
518 * Intel Y-tiling layout
520 * This is a tiled layout using 4Kb tiles (except on gen2 where the tiles 2Kb)
521 * in row-major layout. Within the tile bytes are laid out in OWORD (16 bytes)
522 * chunks column-major, with a platform-dependent height. On top of that the
523 * memory can apply platform-depending swizzling of some higher address bits
526 * Note that this layout is only accurate on intel gen 8+ or valleyview chipsets.
528 * cross-driver sharing. It exists since on a given platform it does uniquely
529 * identify the layout in a simple way for i915-specific userspace, which
536 * Intel Yf-tiling layout
538 * This is a tiled layout using 4Kb tiles in row-major layout.
539 * Within the tile pixels are laid out in 16 256 byte units / sub-tiles which
540 * are arranged in four groups (two wide, two high) with column-major layout.
542 * out as 2x2 column-major.
554 * The main surface will be plane index 0 and must be Y/Yf-tiled,
571 * Intel color control surfaces (CCS) for Gen-12 render compression.
573 * The main surface is Y-tiled and at plane index 0, the CCS is linear and
577 * Y-tile widths.
582 * Intel color control surfaces (CCS) for Gen-12 media compression
584 * The main surface is Y-tiled and at plane index 0, the CCS is linear and
588 * Y-tile widths. For semi-planar formats like NV12, CCS planes follow the
595 * Intel Color Control Surface with Clear Color (CCS) for Gen-12 render
598 * The main surface is Y-tiled and is at plane index 0 whereas CCS is linear
614 * Intel Tile 4 layout
616 * This is a tiled layout using 4KB tiles in a row-major layout. It has the same
637 * The main surface is Tile 4 and at plane index 0. For semi-planar formats
678 * tile4 widths. For semi-planar formats like NV12, CCS planes follow the
704 * Tiled, NV12MT, grouped in 64 (pixels) x 32 (lines) -sized macroblocks
706 * Macroblocks are laid in a Z-shape, and each pixel data is following the
711 * - multiple of 128 pixels for the width
712 * - multiple of 32 pixels for the height
714 * For more information: see https://linuxtv.org/downloads/v4l-dvb-apis/re32.html
719 * Tiled, 16 (pixels) x 16 (lines) - sized macroblocks
721 * This is a simple tiled layout using tiles of 16x16 pixels in a row-major
722 * layout. For YCbCr formats Cb/Cr components are taken in such a way that
731 * Implementation may be platform and base-format specific.
744 * Implementation may be platform and base-format specific.
757 * Implementation may be platform and base-format specific.
765 * Vivante 4x4 tiling layout
767 * This is a simple tiled layout using tiles of 4x4 pixels in a row-major
768 * layout.
773 * Vivante 64x64 super-tiling layout
775 * This is a tiled layout using 64x64 pixel super-tiles, where each super-tile
776 * contains 8x4 groups of 2x4 tiles of 4x4 pixels (like above) each, all in row-
777 * major layout.
780 * https://github.com/etnaviv/etna_viv/blob/master/doc/hardware.md#texture-tiling
785 * Vivante 4x4 tiling layout for dual-pipe
787 * Same as the 4x4 tiling layout, except every second 4x4 pixel tile starts at a
789 * compared to the non-split tiled layout.
794 * Vivante 64x64 super-tiling layout for dual-pipe
796 * Same as the 64x64 super-tiling layout, except every second 4x4 pixel tile
798 * therefore halved compared to the non-split super-tiled layout.
803 * Vivante TS (tile-status) buffer modifiers. They can be combined with all of
810 * clear/compression modifiers, as future cores might add some more TS layout
834 * Tegra Tiled Layout, used by Tegra 2, 3 and 4.
841 * Generalized Block Linear layout, used by desktop GPUs starting with NV50/G80,
844 * Pixels are arranged in Groups of Bytes (GOBs). GOB size and layout varies
855 * ---- ----- -----------------------------------------------------------------
859 * DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK()-based modifiers.
861 * 4:4 - Must be 1, to indicate block-linear layout. Necessary for
863 * DRM_FORMAT_MOD_NVIDIA_16BX2_BLOCK()-based modifiers.
865 * 8:5 - Reserved (To support 3D-surfaces with variable log2(depth) block
873 * 11:9 - Reserved (To support 2D-array textures with variable array stride
878 * tables of all GPUs >= NV50. It affects the exact layout of bits
886 * since the modifier should define the layout of the associated
892 * kind and bit layout has changed at various points.
894 * 0 = Gob Height 8, Fermi - Volta, Tegra K1+ Page Kind mapping
895 * 1 = Gob Height 4, G80 - GT2XX Page Kind mapping
899 * 22:22 s Sector layout. On Tegra GPUs prior to Xavier, there is a further
901 * page kind and block linear swizzles. This causes the layout of
905 * 0 = Tegra K1 - Tegra Parker/TX2 Layout.
906 * 1 = Desktop GPU and Tegra Xavier+ Layout
911 * 1 = ROP/3D, layout 1, exact compression format implied by Page
913 * 2 = ROP/3D, layout 2, exact compression format implied by Page
921 * 55:25 - Reserved for future use. Must be zero.
931 /* To grandfather in prior block linear format modifiers to the above layout,
933 * with block-linear layouts, is remapped within drivers to the value 0xfe,
934 * which corresponds to the "generic" kind used for simple single-sample
935 * uncompressed color formats on Fermi - Volta GPUs.
947 * 16Bx2 Block Linear layout, used by Tegra K1 and later
952 * Within a GOB, data is ordered as 16B x 2 lines sectors laid in Z-shape.
995 ((1ULL << __fourcc_mod_broadcom_param_bits) - 1)))
997 ((m) & ~(((1ULL << __fourcc_mod_broadcom_param_bits) - 1) << \
1003 * This is the primary layout that the V3D GPU can texture from (it
1006 * - 64b utiles of pixels in a raster-order grid according to cpp. It's 4x4
1009 * - 1k subtiles made of a 4x4 raster-order grid of 64b utiles (so usually
1012 * - 4k tiles made of a 2x2 grid of 1k subtiles (so usually 32x32 pixels). On
1016 * - an image made of 4k tiles in rows either left-to-right (even rows of 4k
1017 * tiles) or right-to-left (odd rows of 4k tiles).
1040 * and UV. Some SAND-using hardware stores UV in a separate tiled
1084 * the assumption is that a no-XOR tiling modifier will be created.
1092 * It provides fine-grained random access and minimizes the amount of data
1097 * and different devices or use-cases may support different combinations.
1129 * Multiple superblock sizes are only valid for multi-plane YCbCr formats.
1146 * AFBC block-split
1155 * AFBC sparse layout
1167 * AFBC copy-block restrict
1169 * Buffers with this flag must obey the copy-block restriction. The restriction
1170 * is such that there are no copy-blocks referring across the border of 8x8
1176 * AFBC tiled layout
1178 * The tiled layout groups superblocks in 8x8 or 4x4 tiles, where all
1182 * When the tiled layout is used, the buffer size (in pixels) must be aligned
1190 * Indicates that the buffer makes use of solid-color blocks, whereby bandwidth
1196 * AFBC double-buffer
1198 * Indicates that the buffer is allocated in a layout safe for front-buffer
1206 * Indicates that the buffer includes per-superblock content hints.
1215 * The buffer layout is the same as for AFBC buffers without USM set, this only
1223 * Arm Fixed-Rate Compression (AFRC) modifiers
1225 * AFRC is a proprietary fixed rate image compression protocol and format,
1227 * reductions in graphics and media use-cases.
1234 * fixed size (in bytes). All coding units within a given plane of a buffer
1243 * ---------------- ---------------
1251 * scanline (SCAN layout) or rotated (ROT layout) access.
1253 * Layout Paging Tile Width Paging Tile Height
1254 * ------ ----------------- ------------------
1260 * scanline (SCAN layout) or rotated (ROT layout) access.
1262 * Number of Components in Plane Layout Coding Unit Width Coding Unit Height
1263 * ----------------------------- --------- ----------------- ------------------
1266 * 16x4 chroma 'V' values, in the 'V' plane of a fully-planar YUV buffer
1267 * ----------------------------- --------- ----------------- ------------------
1270 * 8x8 chroma 'V' values, in the 'V' plane of a fully-planar YUV buffer
1271 * ----------------------------- --------- ----------------- ------------------
1273 * Example: 8x4 chroma pairs in the 'UV' plane of a semi-planar YUV buffer
1274 * ----------------------------- --------- ----------------- ------------------
1277 * ----------------------------- --------- ----------------- ------------------
1296 * this is the only plane, while for semi-planar and fully-planar YUV buffers,
1301 * For semi-planar and fully-planar YUV buffers, this corresponds to the chroma plane(s).
1303 * For single-plane buffers, AFRC_FORMAT_MOD_CU_SIZE_P0 must be specified
1305 * For semi-planar and fully-planar buffers, both AFRC_FORMAT_MOD_CU_SIZE_P0 and
1317 * AFRC scanline memory layout.
1319 * Indicates if the buffer uses the scanline-optimised layout
1320 * for an AFRC encoded buffer, otherwise, it uses the rotation-optimised layout.
1321 * The memory layout is the same for all planes.
1326 * Arm 16x16 Block U-Interleaved modifier
1345 * both in row-major order.
1359 * The underlying storage is considered to be 3 components, 8bit or 10-bit
1361 * - DRM_FORMAT_YUV420_8BIT
1362 * - DRM_FORMAT_YUV420_10BIT
1364 * The first 8 bits of the mode defines the layout, then the following 8 bits
1365 * defines the options changing the layout.
1368 * combinations of layout and options.
1383 * Amlogic FBC Basic Layout
1385 * The basic layout is composed of:
1386 * - a body content organized in 64x32 superblocks with 4096 bytes per
1388 * - a 32 bytes per 128x64 header block
1390 * This layout is transferrable between Amlogic SoCs supporting this modifier.
1395 * Amlogic FBC Scatter Memory layout
1398 * frames content to optimize memory access and layout.
1405 * Due to the nature of the layout, these buffers are not expected to
1406 * be accessible by the user-space clients, but only accessible by the
1409 * The user-space clients should expect a failure while trying to mmap
1410 * the DMA-BUF handle returned by the producer.
1414 /* Amlogic FBC Layout Options Bit Mask */
1423 * This mode reduces body layout to 3072 bytes per 64x32 superblock with
1424 * the basic layout and 3200 bytes per 64x32 superblock combined with
1425 * the scatter layout.
1432 * Memory layout:
1435 * - main surface
1438 * - main surface in plane 0
1439 * - DCC surface in plane 1 (RB-aligned, pipe-aligned if DCC_PIPE_ALIGN is set)
1442 * - main surface in plane 0
1443 * - displayable DCC surface in plane 1 (not RB-aligned & not pipe-aligned)
1444 * - pipe-aligned DCC surface in plane 2 (RB-aligned & pipe-aligned)
1446 * For multi-plane formats the above surfaces get merged into one plane for
1450 * ----- ------------------------ ---------------------------------------------
1466 * 55:36 - Reserved for future use, must be zero
1485 * 64K_D for non-32 bpp is the same for GFX9/GFX10/GFX10_RBPLUS and hence has
1509 * one which is not-aligned.