Searched full:laid (Results 1 – 25 of 100) sorted by relevance
1234
| /linux-5.10/drivers/md/ |
| D | raid10.h | 37 int near_copies; /* number of copies laid out
39 int far_copies; /* number of copies laid out
|
| /linux-5.10/include/drm/ |
| D | drm_fourcc.h | 148 * 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)
|
| /linux-5.10/drivers/net/ethernet/intel/igc/ |
| D | igc_diag.h | 16 /* In the hardware, registers are laid out either singly, in arrays
|
| /linux-5.10/Documentation/scsi/ |
| D | sym53c500_cs.rst | 22 other products using this chip, but I've never laid eyes (much less hands)
|
| /linux-5.10/include/linux/ |
| D | packing.h | 22 * format. Unpacked means laid out in memory in the CPU's native
|
| D | page-flags-layout.h | 39 * There are five possibilities for how page->flags get laid out. The first
|
| /linux-5.10/tools/testing/selftests/arm64/signal/ |
| D | signals.S | 48 * For simplicity this assumes that current field 'token' is laid out
|
| /linux-5.10/include/uapi/rdma/ |
| D | cxgb4-abi.h | 41 * Make sure that all structs defined in this file remain laid out so
|
| D | mthca-abi.h | 47 * Make sure that all structs defined in this file remain laid out so
|
| D | mlx4-abi.h | 49 * Make sure that all structs defined in this file remain laid out so
|
| /linux-5.10/arch/sparc/include/uapi/asm/ |
| D | psr.h | 15 /* The Sparc PSR fields are laid out as the following:
|
| /linux-5.10/arch/openrisc/include/asm/ |
| D | ptrace.h | 31 * This struct describes how the registers are laid out on the kernel stack
|
| /linux-5.10/arch/arm64/xen/ |
| D | hypercall.S | 46 * Parameter structs passed to hypercalls are laid out according to
|
| /linux-5.10/arch/powerpc/include/asm/ |
| D | pgtable.h | 23 /* Note due to the way vm flags are laid out, the bits are XWR */
|
| /linux-5.10/Documentation/block/ |
| D | deadline-iosched.rst | 63 or a front merge candidate. Due to the way files are typically laid out,
|
| /linux-5.10/include/asm-generic/ |
| D | iomap.h | 78 * want MMIO that copies stuff laid out in MMIO
|
| /linux-5.10/include/uapi/linux/ |
| D | virtio_balloon.h | 95 * NOTE: fields are laid out in a way that would make compiler add padding
|
| /linux-5.10/arch/m68k/mac/ |
| D | oss.c | 96 * This IRQ mapping is laid out with two things in mind: first, we try to keep
|
| /linux-5.10/include/uapi/drm/ |
| D | drm_fourcc.h | 401 * in row-major layout. Within the tile bytes are laid out row-major, with
418 * in row-major layout. Within the tile bytes are laid out in OWORD (16 bytes)
436 * Within the tile pixels are laid out in 16 256 byte units / sub-tiles which
438 * Each group therefore consits out of four 256 byte units, which are also laid
494 * Macroblocks are laid in a Z-shape, and each pixel data is following the
689 * Within a GOB, data is ordered as 16B x 2 lines sectors laid in Z-shape.
|
| /linux-5.10/Documentation/misc-devices/ |
| D | eeprom.rst | 64 organization laid out by Frodo, but it should be at least completely
|
| /linux-5.10/arch/alpha/include/asm/ |
| D | elf.h | 106 /* The registers are laid out in pt_regs for PAL and syscall
|
| /linux-5.10/Documentation/devicetree/bindings/display/imx/ |
| D | ldb.txt | 69 This describes how the color bits are laid out in the
|
| /linux-5.10/Documentation/devicetree/bindings/pci/ |
| D | host-generic-pci.yaml | 22 accessed via an ioport) and laid out with a direct correspondence to the
|
| /linux-5.10/Documentation/filesystems/ext4/ |
| D | group_descr.rst | 43 The block group descriptor is laid out in ``struct ext4_group_desc``.
|
| /linux-5.10/Documentation/devicetree/bindings/gpio/ |
| D | nvidia,tegra186-gpio.txt | 38 are grouped and laid out according to the port they affect.
|
1234