/linux/include/drm/ |
H A 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/Documentation/ABI/testing/ |
H A D | sysfs-driver-tegra-fuse | 6 data programmed at the factory. The data is laid out in 32bit
|
/linux/drivers/net/ethernet/intel/igc/ |
H A D | igc_diag.h | 16 /* In the hardware, registers are laid out either singly, in arrays
|
/linux/Documentation/scsi/ |
H A D | sym53c500_cs.rst | 22 other products using this chip, but I've never laid eyes (much less hands)
|
/linux/tools/testing/selftests/arm64/signal/ |
H A D | signals.S | 48 * For simplicity this assumes that current field 'token' is laid out
|
/linux/include/linux/ |
H A D | litex.h | 30 * 32-bit wide logical CSR will be laid out as four 32-bit physical
|
H A D | page-flags-layout.h | 40 * There are five possibilities for how page->flags get laid out. The first
|
/linux/arch/sparc/include/uapi/asm/ |
H A D | psr.h | 15 /* The Sparc PSR fields are laid out as the following:
|
/linux/include/uapi/rdma/ |
H A D | cxgb4-abi.h | 41 * Make sure that all structs defined in this file remain laid out so
|
H A D | mthca-abi.h | 47 * Make sure that all structs defined in this file remain laid out so
|
H A D | mlx4-abi.h | 49 * Make sure that all structs defined in this file remain laid out so
|
/linux/include/asm-generic/ |
H A D | iomap.h | 58 * want MMIO that copies stuff laid out in MMIO
|
/linux/Documentation/block/ |
H A D | deadline-iosched.rst | 63 or a front merge candidate. Due to the way files are typically laid out,
|
/linux/arch/m68k/mac/ |
H A D | oss.c | 98 * This IRQ mapping is laid out with two things in mind: first, we try to keep
|
/linux/include/uapi/linux/ |
H A D | virtio_balloon.h | 107 * NOTE: fields are laid out in a way that would make compiler add padding
|
/linux/arch/openrisc/include/asm/ |
H A D | ptrace.h | 32 * This struct describes how the registers are laid out on the kernel stack
|
/linux/Documentation/filesystems/ext4/ |
H A D | group_descr.rst | 43 The block group descriptor is laid out in ``struct ext4_group_desc``.
|
/linux/arch/alpha/include/asm/ |
H A D | elf.h | 106 /* The registers are laid out in pt_regs for PAL and syscall
|
/linux/arch/x86/include/asm/ |
H A D | pgtable_64_types.h | 138 * belonging to vmalloc area is now laid out as follows:
|
/linux/Documentation/devicetree/bindings/pci/ |
H A D | host-generic-pci.yaml | 22 accessed via an ioport) and laid out with a direct correspondence to the
|
/linux/Documentation/userspace-api/ |
H A D | dma-buf-alloc-exchange.rst | 73 A description of how pixel data is laid out in memory buffers. 123 is laid out row-sequentially, from the top-left to the bottom-right corner.
|
/linux/drivers/ata/ |
H A D | pata_ninja32.c | 13 * laid out as follows off BAR 0. This is based upon Mark Lord's delkin
|
/linux/arch/mips/sgi-ip22/ |
H A D | ip22-mc.c | 125 * as it can correctly operate. The register is laid in sgimc_init()
|
/linux/Documentation/gpu/ |
H A D | afbc.rst | 14 All users of the AFBC modifiers must follow the usage guidelines laid
|
/linux/drivers/net/wireless/broadcom/b43/ |
H A D | phy_g.h | 168 * Each value in the stack is laid out as follows:
|