Home
last modified time | relevance | path

Searched full:laid (Results 1 – 25 of 183) sorted by relevance

12345678

/OK3568_Linux_fs/kernel/include/drm/
H A Ddrm_fourcc.h148 * format with data laid in a single plane
162 * format with data laid in two planes (luminance and chrominance)
176 * format with data laid in three planes (one for each YUV component)
/OK3568_Linux_fs/kernel/drivers/md/
H A Draid10.h37 int near_copies; /* number of copies laid out
39 int far_copies; /* number of copies laid out
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/include/drm/
H A Ddrm_fourcc.h266 * in row-major layout. Within the tile bytes are laid out row-major, with
280 * in row-major layout. Within the tile bytes are laid out in OWORD (16 bytes)
295 * Within the tile pixels are laid out in 16 256 byte units / sub-tiles which
297 * Each group therefore consits out of four 256 byte units, which are also laid
329 * Macroblocks are laid in a Z-shape, and each pixel data is following the
418 * Within a GOB, data is ordered as 16B x 2 lines sectors laid in Z-shape.
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc/usr/include/drm/
H A Ddrm_fourcc.h266 * in row-major layout. Within the tile bytes are laid out row-major, with
280 * in row-major layout. Within the tile bytes are laid out in OWORD (16 bytes)
295 * Within the tile pixels are laid out in 16 256 byte units / sub-tiles which
297 * Each group therefore consits out of four 256 byte units, which are also laid
329 * Macroblocks are laid in a Z-shape, and each pixel data is following the
418 * Within a GOB, data is ordered as 16B x 2 lines sectors laid in Z-shape.
/OK3568_Linux_fs/kernel/drivers/net/ethernet/intel/igc/
H A Digc_diag.h16 /* In the hardware, registers are laid out either singly, in arrays
/OK3568_Linux_fs/kernel/Documentation/scsi/
H A Dsym53c500_cs.rst22 other products using this chip, but I've never laid eyes (much less hands)
/OK3568_Linux_fs/external/linux-rga/samples/utils/3rdparty/libdrm/include/libdrm/
H A Ddrm_fourcc.h353 * in row-major layout. Within the tile bytes are laid out row-major, with
367 * in row-major layout. Within the tile bytes are laid out in OWORD (16 bytes)
382 * Within the tile pixels are laid out in 16 256 byte units / sub-tiles which
384 * Each group therefore consists out of four 256 byte units, which are also laid
416 * Macroblocks are laid in a Z-shape, and each pixel data is following the
505 * Within a GOB, data is ordered as 16B x 2 lines sectors laid in Z-shape.
/OK3568_Linux_fs/external/linux-rga/samples/im2d_slt/third-party/libdrm/include/libdrm/
H A Ddrm_fourcc.h353 * in row-major layout. Within the tile bytes are laid out row-major, with
367 * in row-major layout. Within the tile bytes are laid out in OWORD (16 bytes)
382 * Within the tile pixels are laid out in 16 256 byte units / sub-tiles which
384 * Each group therefore consists out of four 256 byte units, which are also laid
416 * Macroblocks are laid in a Z-shape, and each pixel data is following the
505 * Within a GOB, data is ordered as 16B x 2 lines sectors laid in Z-shape.
/OK3568_Linux_fs/external/camera_engine_rkaiq/rkisp_demo/demo/include/libdrm/
H A Ddrm_fourcc.h353 * in row-major layout. Within the tile bytes are laid out row-major, with
367 * in row-major layout. Within the tile bytes are laid out in OWORD (16 bytes)
382 * Within the tile pixels are laid out in 16 256 byte units / sub-tiles which
384 * Each group therefore consists out of four 256 byte units, which are also laid
416 * Macroblocks are laid in a Z-shape, and each pixel data is following the
505 * Within a GOB, data is ordered as 16B x 2 lines sectors laid in Z-shape.
/OK3568_Linux_fs/u-boot/drivers/video/fonts/
H A DKconfig36 A laid-back handwritten font.
/OK3568_Linux_fs/kernel/tools/testing/selftests/arm64/signal/
H A Dsignals.S48 * For simplicity this assumes that current field 'token' is laid out
/OK3568_Linux_fs/kernel/include/linux/
H A Dpacking.h22 * format. Unpacked means laid out in memory in the CPU's native
H A Dpage-flags-layout.h39 * There are five possibilities for how page->flags get laid out. The first
/OK3568_Linux_fs/u-boot/doc/device-tree-bindings/video/
H A Drockchip-lvds.txt16 This describes how the color bits are laid out in the
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/include/rdma/
H A Dcxgb3-abi.h41 * Make sure that all structs defined in this file remain laid out so
H A Dmthca-abi.h47 * Make sure that all structs defined in this file remain laid out so
H A Dcxgb4-abi.h41 * Make sure that all structs defined in this file remain laid out so
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc/usr/include/rdma/
H A Dcxgb3-abi.h41 * Make sure that all structs defined in this file remain laid out so
H A Dmthca-abi.h47 * Make sure that all structs defined in this file remain laid out so
H A Dcxgb4-abi.h41 * Make sure that all structs defined in this file remain laid out so
/OK3568_Linux_fs/kernel/include/uapi/rdma/
H A Dmthca-abi.h47 * Make sure that all structs defined in this file remain laid out so
H A Dcxgb4-abi.h41 * Make sure that all structs defined in this file remain laid out so
/OK3568_Linux_fs/kernel/arch/sparc/include/uapi/asm/
H A Dpsr.h15 /* The Sparc PSR fields are laid out as the following:
/OK3568_Linux_fs/kernel/arch/openrisc/include/asm/
H A Dptrace.h31 * This struct describes how the registers are laid out on the kernel stack
/OK3568_Linux_fs/u-boot/arch/arm/include/asm/ti-common/
H A Dti-edma3.h59 /* PaRAM slots are laid out like this */

12345678