Searched full:layout (Results 1 – 25 of 242) sorted by relevance
12345678910
| /Documentation/filesystems/nfs/ |
| D | pnfs.rst | 17 Each nfs_inode may hold a pointer to a cache of these layout
18 segments in nfsi->layout, of type struct pnfs_layout_hdr.
26 the reference count, as the layout is kept around by the lseg that
33 layout driver type. The device ids are held in a RCU cache (struct
62 layout drivers
65 PNFS utilizes what is called layout drivers. The STD defines 4 basic
66 layout types: "files", "objects", "blocks", and "flexfiles". For each
67 of these types there is a layout-driver with a common function-vectors
69 different layout types.
71 Files-layout-driver code is in: fs/nfs/filelayout/.. directory
[all …]
|
| /Documentation/devicetree/bindings/nvmem/layouts/ |
| D | fixed-layout.yaml | 4 $id: http://devicetree.org/schemas/nvmem/layouts/fixed-layout.yaml#
7 title: NVMEM layout for fixed NVMEM cells
10 Many NVMEM devices have hardcoded cells layout (offset and size of defined
13 This binding allows defining such NVMEM layout with its cells. It can be used
21 const: fixed-layout
42 nvmem-layout {
43 compatible = "fixed-layout";
|
| D | onie,tlv-layout.yaml | 4 $id: http://devicetree.org/schemas/nvmem/layouts/onie,tlv-layout.yaml#
7 title: NVMEM layout of the ONIE tlv table
26 const: onie,tlv-layout
116 nvmem-layout {
117 compatible = "onie,tlv-layout";
137 nvmem-layout {
138 compatible = "onie,tlv-layout";
|
| D | nvmem-layout.yaml | 4 $id: http://devicetree.org/schemas/nvmem/layouts/nvmem-layout.yaml#
18 perform their parsing. The nvmem-layout container is here to describe these.
21 - $ref: fixed-layout.yaml
23 - $ref: onie,tlv-layout.yaml
|
| D | kontron,sl28-vpd.yaml | 7 title: NVMEM layout of the Kontron SMARC-sAL28 vital product data
52 nvmem-layout {
|
| /Documentation/gpu/xe/ |
| D | xe_firmware.rst | 7 Firmware Layout
11 :doc: CSS-based Firmware Layout
14 :doc: GSC-based Firmware Layout
16 Write Once Protected Content Memory (WOPCM) Layout
20 :doc: Write Once Protected Content Memory (WOPCM) Layout
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | nvmem.yaml | 42 nvmem-layout:
43 $ref: /schemas/nvmem/layouts/nvmem-layout.yaml
46 container may reference more advanced (dynamic) layout
65 nvmem-layout {
66 compatible = "fixed-layout";
|
| D | xlnx,zynqmp-nvmem.yaml | 33 nvmem-layout {
34 compatible = "fixed-layout";
|
| /Documentation/devicetree/bindings/mtd/partitions/ |
| D | ubi-volume.yaml | 27 nvmem-layout:
28 $ref: /schemas/nvmem/layouts/nvmem-layout.yaml#
30 This container may reference an NVMEM layout parser.
|
| D | linux,ubi.yaml | 63 nvmem-layout {
64 compatible = "fixed-layout";
|
| D | tplink,safeloader-partitions.yaml | 11 flash layout, firmware, product info, configuration, calibration
14 Flash space layout of TP-Link devices is stored on flash itself using
|
| /Documentation/devicetree/bindings/usb/ |
| D | fcs,fsa4480.yaml | 55 Default AUX/SBU layout (FSA4480)
58 Default AUX/SBU layout (OCP96011)
65 Swapped AUX/SBU layout (FSA4480)
68 Swapped AUX/SBU layout (OCP96011)
|
| /Documentation/arch/arm/samsung/ |
| D | overview.rst | 31 Layout chapter
34 The directory layout is currently being restructured, and consists of
48 Layout changes
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-iio-sx9324 | 6 SX9324 has 3 inputs, CS0, CS1 and CS2. Hardware layout
28 Note, these are the chip default. Hardware layout will most
|
| D | sysfs-class-intel_pmt | 19 of the device. The register layout of the telemetry space is
38 be used to get the register layout.
65 resulting crashlog buffer. The register layout for the buffer
84 used to determine the register layout.
|
| D | sysfs-firmware-gsmi | 17 Layout:
21 This directory has the same layout (and
|
| D | sysfs-driver-intel_sdsi | 36 the layout of the registers file in this directory.
46 a CPU and monitor status information. The layout of this file
48 the layout for a particular GUID is available at
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | aspeed,ast2400-vic.yaml | 13 The AST2400 and AST2500 SoC families include a legacy register layout before
14 a redesigned layout, but the bindings do not prescribe the use of one or the
|
| /Documentation/driver-api/pldmfw/ |
| D | file-format.rst | 14 overall file layout
59 header layout
92 area layout
115 record layout
147 area layout
170 component layout
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-raid.rst | 26 - Transitory layout
51 layout for takeover from/to raid4/raid5_n
54 - layout for takeover from raid5_la from/to raid6
57 - layout for takeover from raid5_ra from/to raid6
60 - layout for takeover from raid5_ls from/to raid6
63 - layout for takeover from raid5_rs from/to raid6
114 These two options are used to alter the default layout of
133 The 2-device layout is equivalent 2-way RAID1. The 4-device
134 layout is what a traditional RAID10 would look like. The
135 3-device layout is what might be called a 'RAID1E - Integrated
[all …]
|
| /Documentation/admin-guide/nfs/ |
| D | pnfs-block-server.rst | 2 pNFS block layout server user guide
5 The Linux NFS server now supports the pNFS block layout extension. In this
|
| /Documentation/arch/s390/ |
| D | mm.rst | 7 Virtual memory layout
12 - Some aspects of the virtual memory layout setup are not
15 - Unused gaps in the virtual memory layout could be present
|
| /Documentation/admin-guide/media/ |
| D | si476x.rst | 34 following layout:
68 has the following layout:
84 The layout is:
109 The layout is:
159 RSQ(Received Signal Quality) for primary tuner only. Layout is as
|
| /Documentation/filesystems/ext4/ |
| D | blockgroup.rst | 3 Layout chapter
6 The layout of a standard block group is approximately as follows (each
112 descriptor layout, or existing filesystems can be resized on-line, and
114 block group using this new layout.
|
| /Documentation/arch/arm/ |
| D | memory.rst | 2 Kernel Memory Layout on ARM Linux
9 This document describes the virtual memory layout which the Linux
100 Since future CPUs may impact the kernel mapping layout, user programs
|
12345678910