Home
last modified time | relevance | path

Searched full:layouts (Results 1 – 25 of 101) sorted by relevance

12345

/linux/Documentation/devicetree/bindings/nvmem/layouts/
H A Dnvmem-layout.yaml4 $id: http://devicetree.org/schemas/nvmem/layouts/nvmem-layout.yaml#
7 title: NVMEM (Non Volatile Memory) layouts
15 Most NVMEM layouts are static and thus do not require additional description
16 besides the bytes/bits offset and length. Other layouts can be less statically
H A Dfixed-cell.yaml4 $id: http://devicetree.org/schemas/nvmem/layouts/fixed-cell.yaml#
H A Dkontron,sl28-vpd.yaml4 $id: http://devicetree.org/schemas/nvmem/layouts/kontron,sl28-vpd.yaml#
H A Dfixed-layout.yaml4 $id: http://devicetree.org/schemas/nvmem/layouts/fixed-layout.yaml#
/linux/Documentation/driver-api/
H A Dnvmem.rst183 8. NVMEM layouts
186 NVMEM layouts are yet another mechanism to create cells. With the device
191 be added accordingly. Layouts let you read the content of the NVMEM device
194 Another use case for layouts is the post processing of cells. With layouts,
/linux/Documentation/devicetree/bindings/nvmem/
H A Dnvmem-deprecated-cells.yaml13 Before introducing NVMEM layouts all NVMEM (fixed) cells were defined
21 - $ref: layouts/fixed-cell.yaml
H A Dst,stm32-romem.yaml36 $ref: layouts/fixed-cell.yaml
H A Dnvmem.yaml43 $ref: /schemas/nvmem/layouts/nvmem-layout.yaml
/linux/drivers/net/ethernet/sfc/
H A Dfw_formats.h14 /* Header layouts of firmware update images recognised by Efx NICs.
15 * The sources-of-truth for these layouts are AMD internal documents
/linux/Documentation/filesystems/nfs/
H A Dpnfs.rst5 The are several inter-related caches. We have layouts which can
8 can be referenced by multiple layouts. To keep all of this straight,
/linux/tools/virtio/ringtest/
H A DREADME1 Partial implementation of various ring layouts, useful to tune virtio design.
/linux/include/linux/dma/
H A Dedma.h62 * must be preserved, and layouts with shared
64 * direction granularity. Layouts with per-channel
/linux/drivers/nvmem/layouts/
H A DMakefile3 # Makefile for nvmem layouts.
/linux/arch/parisc/include/asm/
H A Dsparsemem.h5 /* We have these possible memory map layouts:
/linux/Documentation/devicetree/bindings/mtd/partitions/
H A Dubi-volume.yaml28 $ref: /schemas/nvmem/layouts/nvmem-layout.yaml#
/linux/drivers/md/
H A Draid0.h17 * The layouts are identical when there is only one zone (all
/linux/Documentation/devicetree/bindings/display/
H A Dlvds.yaml20 data formats and layouts is used to drive LVDS displays.
/linux/include/linux/
H A Delfcore-compat.h10 * Make sure these layouts match the linux/elfcore.h native definitions.
/linux/arch/sparc/include/uapi/asm/
H A Ductx.h3 * uctx.h: Sparc64 {set,get}context() register state layouts.
/linux/Documentation/userspace-api/media/v4l/
H A Dpixfmt-yuv-planar.rst392 The layouts of the luma and chroma planes are identical.
400 tiles is stored in linear order. The layouts of the luma and chroma
421 aligned to a multiple of 4. The layouts of the luma and chroma planes are
426 aligned to a multiple of 16. The layouts of the luma and chroma planes are
431 aligned to a multiple of 32. The layouts of the luma and chroma planes are
437 The layouts of the luma and chroma planes are identical.
467 The layouts of the luma and chroma planes are identical.
980 a multiple of 4. The layouts of the luma and chroma planes are identical.
/linux/rust/kernel/mm/
H A Dmmput_async.rs65 // SAFETY: The layouts and invariants are compatible. in into_mmput_async()
/linux/include/drm/
H A Ddrm_framebuffer.h163 * storage buffer object. For tiled layouts this generally means its
174 * tiling, or also special layouts (like compression) of auxiliary
/linux/Documentation/devicetree/bindings/soc/fsl/cpm_qe/
H A Dgpio.txt4 On CPM1 devices, all ports are using slightly different register layouts.
/linux/arch/sh/kernel/vsyscall/
H A Dvsyscall.lds.S33 * For the layouts to match, we need to skip more than enough
/linux/arch/arm/include/asm/
H A Ducontext.h35 * coprocessor's layouts are part of the userspace ABI. Each one of

12345