Searched full:area (Results 1 – 25 of 303) sorted by relevance
12345678910>>...13
| /Documentation/ABI/testing/ |
| D | sysfs-devices-mmc | 5 Enhanced area is a new feature defined in eMMC4.4 standard.
7 area can help to improve the card performance. If the feature
9 enhanced data area. If not, this attribute will be -EINVAL.
16 Enhanced area is a new feature defined in eMMC4.4 standard.
18 area can help to improve the card performance. If the feature
20 data area. If not, this attribute will be -EINVAL.
|
| D | sysfs-bus-iio-light-si1133 | 6 dark photodiode. "small" indicate the surface area capturing
14 dark photodiodes. "large" indicate the surface area capturing
|
| D | securityfs-secrets-coco | 8 EFI can declare memory area used by confidential computing
18 if the EFI secret area is populated.
51 the EFI secret area".
|
| /Documentation/admin-guide/mm/ |
| D | cma_debugfs.rst | 8 Each CMA area represents a directory under <debugfs>/cma/, represented by
16 - [RO] count: Amount of memory in the CMA area.
19 - [WO] alloc: Allocate N pages from that CMA area. For example::
23 would try to allocate 5 pages from the 'cma_name' area.
25 - [WO] free: Free N pages from that CMA area, similar to the above.
|
| D | userfaultfd.rst | 219 difference between writes into a WP area and into a !WP area. The
382 non-cooperative process moves a virtual memory area to a
385 new addresses of the area and its original length.
391 will contain start and end addresses of the removed area.
396 end addresses of the unmapped area.
401 removed, but the area is not, the area remains monitored by the
402 ``userfaultfd``, and if a page fault occurs in that area it will be
405 area is unmapped, either explicitly (with munmap() system call), or
406 implicitly (e.g. during mremap()), the area is removed and in turn the
407 ``userfaultfd`` context for such area disappears too and the manager will
[all …]
|
| /Documentation/arch/s390/ |
| D | 3270.rst | 201 The driver defines three areas on the 3270 screen: the log area, the
202 input area, and the status area.
204 The log area takes up all but the bottom two lines of the screen. The
206 down. When it fills, the status area changes from "Linux Running" to
210 The input area extends from the beginning of the second-to-last screen
211 line to the start of the status area. You type commands in this area
214 The status area initializes to "Linux Running" to give you a warm
215 fuzzy feeling. When the log area fills up and output awaits, it
219 the input area to toggle between "Linux More..." and "Linux Holding",
231 Other things you may do when the log area fills up are: hit PA2 to
[all …]
|
| D | mm.rst | 26 | Physical | Virtual | VM area description
87 +- VMALLOC_START --+ vmalloc area start
89 | vmalloc area | KASAN shallowly populated in case
91 +- MODULES_VADDR --+ modules area start
93 | modules area | KASAN shallowly populated in case
|
| D | s390dbf.rst | 29 where exactly one is active at one time. Each debug area consists of contiguous
34 area and updates the log pointer for the active area. If the end
35 of the active debug area is reached, a wrap around is done (ring buffer)
37 debug area.
40 switches to the next debug area. This is done in order to be sure
42 overwritten when a wrap around for the current area occurs.
45 When an exception is thrown in the last debug area, the following debug
46 entries are then written again in the very first area.
231 area (0...n) to the debugfs file "flush". When using "-" all debug areas
236 1. Flush debug area 0::
[all …]
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-integrity.rst | 41 Accesses to the on-disk metadata area containing checksums (aka tags) are
42 buffered using dm-bufio. When an access to any given metadata area
43 occurs, each unique metadata area gets its own buffer(s). The buffer size
44 is capped at the size of the metadata area, but may be smaller, thereby
45 requiring multiple buffers to represent the full metadata area. A smaller
47 metadata area for small reads/writes. The metadata is still read even in
189 Use a smaller padding of the tag area that is more
218 bytes, it will take 128 KiB of tags to track a full data area, requiring
219 256 sectors of metadata per data area. With the default buffer_sectors of
220 128, that means there will be 2 buffers per metadata area, or 2 buffers
[all …]
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | mpc8xxx-wdt.txt | 8 - reg: base physical address and length of the area hosting the
10 On the 83xx, "Watchdog Timer Registers" area: <0x200 0x100>
11 On the 86xx, "Watchdog Timer Registers" area: <0xe4000 0x100>
12 On the 8xx, "General System Interface Unit" area: <0x0 0x10>
|
| /Documentation/userspace-api/media/v4l/ |
| D | metafmt-vsp1-hgt.rst | 43 Area 0 Area 1 Area 2 Area 3 Area 4 Area 5
59 value is considered as part of the lower area.
61 Pixels with a hue value included in the centre of an area (between nL and nU
62 included) are attributed to that single area and given a weight of 16. Pixels
68 The Hue area setup must match one of the following constrains:
|
| D | selection-api-configuration.rst | 8 select an area in a video signal or a buffer, and to query for default
37 the area actually sampled, is given by the ``V4L2_SEL_TGT_CROP`` target.
39 active cropping area must lie completely inside the capture boundaries.
74 padded area but outside active area is undefined. The application can
96 the area from which image date are processed by the hardware, is given
98 same coordinate system as the bounds rectangle. The active cropping area
111 driver must adjust the area to fit to the bounding limits. Moreover, the
123 However, such a padded area is driver-dependent feature not covered by
|
| D | crop.rst | 24 Applications can use the following API to select an area in the video
25 signal, query the default area and the hardware limits.
35 the area actually sampled. The target are images read by the application
44 the video signal, and the cropping ioctls determine the area where the
75 height of the area which can be sampled is given by the ``bounds``
87 the area actually sampled, is given by struct
98 shall align with the center of the active picture area of the video
119 :c:type:`v4l2_cropcap`. ``bounds`` area. Therefore, as
124 they may prefer a particular image size or a certain area in the video
144 Now the application may insist on covering an area using a picture
[all …]
|
| /Documentation/security/secrets/ |
| D | coco.rst | 28 The guest firmware may reserve a designated memory area for secret injection,
31 (``adf956ad-e98c-484c-ae11-b51c7d336447``). This memory area should be marked
36 area. In AMD SEV and SEV-ES this is performed using the
40 "Structure of the EFI secret area".
42 On kernel start, the kernel's EFI driver saves the location of the secret area
44 Later it checks if the secret area is populated: it maps the area and checks
46 (``1e74f542-71dd-4d66-963e-ef4287ff173b``). If the secret area is populated,
68 to which an EFI secret area with 4 secrets was injected during launch::
|
| /Documentation/arch/xtensa/ |
| D | mmu.rst | 64 6. The IO area covers the entire 256MB segment of parent-bus-address; the
83 | VMALLOC area | VMALLOC_START 0xc0000000 128MB - 64KB
87 | remap area 1 |
90 | remap area 2 |
93 | KMAP area | PKMAP_BASE PTRS_PER_PTE *
98 | Atomic KMAP area | FIXADDR_START KM_TYPE_NR *
126 | VMALLOC area | VMALLOC_START 0xa0000000 128MB - 64KB
130 | remap area 1 |
133 | remap area 2 |
136 | KMAP area | PKMAP_BASE PTRS_PER_PTE *
[all …]
|
| /Documentation/arch/sparc/oradax/ |
| D | oracle-dax.rst | 41 pointer to a "completion area", which is a 128 byte memory block that
43 interrupt is generated upon completion; the completion area must be
96 requests. The completion area buffer is also allocated, and this is
142 completion area to use, and may be set via lseek() or using the
157 The mmap() function provides access to the completion area allocated
158 in the driver. Note that the completion area is not writeable by the
165 The first byte in each completion area is the command status which is
185 - call mmap() to get the completion area address
192 - call munmap() for completion area
236 for the completion area, output buffer, and various inputs::
[all …]
|
| /Documentation/arch/arm/ |
| D | porting.rst | 29 Start address of zero-initialised work area for the decompressor.
77 area, and therefore managed dynamically on a process by process
97 Virtual addresses bounding the vmalloc() area. There must not be
98 any static mappings in this area; vmalloc will overwrite them.
100 Normally, the vmalloc() area starts VMALLOC_OFFSET bytes above the
105 between virtual RAM and the vmalloc area. We do this to allow
|
| /Documentation/filesystems/ |
| D | qnx6.rst | 167 Bitmap system area
172 First the system area, that is split into two halves.
176 The requirement for a static, fixed preallocated system area comes from how
179 Each superblock got its own half of the system area. So superblock #1
181 blocks represented by the upper half bitmap system area bits.
187 (system area of the inactive - resp. lower serial numbered superblock) while
189 other half of the system area.
196 For all data outside the system area, blocks are just copied while writing.
|
| /Documentation/devicetree/bindings/mtd/ |
| D | raw-nand-chip.yaml | 38 known to be stored in the OOB area, or "interleaved" if ECC
39 bytes will be interleaved with regular data in the main area.
64 it as the device ages. Otherwise, the out-of-band area of a
75 providing the best strength and taking the OOB area size
77 only the in-band area is used by the upper layers, and you
|
| /Documentation/arch/arm64/ |
| D | kdump.rst | 22 be considered if the crashkernel is reserved from the high memory area.
31 For kdump reservations, low memory is the memory area under a specific
56 Firstly, the kernel searches the low memory area for an available region
60 the high memory area for an available region of the specified size. If
76 from this area should be kept to a minimum.
|
| /Documentation/devicetree/bindings/nvmem/ |
| D | st,stm32-romem.yaml | 10 This represents STM32 Factory-programmed read only non-volatile area: locked
42 This property explicits a factory programmed area that both secure
44 related area can only be reached by the secure world.
|
| /Documentation/core-api/ |
| D | this_cpu_ops.rst | 11 the cpu permanently stored the beginning of the per cpu area for a
37 Please note that accesses by remote processors to a per cpu area are
68 per cpu area. It is then possible to simply use the segment override
69 to relocate a per cpu relative address to the proper per cpu area for
138 available. Instead, the offset of the local per cpu area is simply
152 area. They do not have addresses although they look like that in the
154 added to a base pointer of a per cpu area of a processor in order to
287 the remote CPU and perform the update to its per cpu area.
298 area remotely.
331 of a remote write to the per cpu area of another processor.
[all …]
|
| D | swiotlb.rst | 163 entirely in a single area. Each area has its own spin lock that must be held to
164 manipulate the slots in that area. The division into areas avoids contending
167 maximum parallelism, but since an area can't be smaller than IO_TLB_SEGSIZE
168 slots, it might be necessary to assign multiple CPUs to the same area. The
171 When allocating a bounce buffer, if the area associated with the calling CPU
173 sequentially. For each area tried, the area's spin lock must be obtained before
220 of 4 MiB and the 256 KiB minimum area size, only 16 areas can be created. If
221 the system has more than 16 CPUs, multiple CPUs must share an area, creating
249 io_tlb_area describes an area. The primary field is the spin lock used to
250 serialize access to slots in the area. The io_tlb_area array for a pool has an
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | stericsson,u8500-clks.yaml | 31 - description: PRCC 1 register area
32 - description: PRCC 2 register area
33 - description: PRCC 3 register area
34 - description: PRCC 5 register area
35 - description: PRCC 6 register area
|
| /Documentation/arch/powerpc/ |
| D | kasan.txt | 8 The shadow area sits at the top of the kernel virtual memory space above the
9 fixmap area and occupies one eighth of the total kernel virtual memory space.
11 Instrumentation of the vmalloc area is optional, unless built with modules,
|
12345678910>>...13