Searched refs:areas (Results 1 – 25 of 147) sorted by relevance
123456
| /Linux-v5.4/arch/s390/kernel/ |
| D | debug.c | 194 debug_entry_t ***areas; in debug_areas_alloc() local
197 areas = kmalloc_array(nr_areas, sizeof(debug_entry_t **), GFP_KERNEL); in debug_areas_alloc()
198 if (!areas) in debug_areas_alloc()
201 areas[i] = kmalloc_array(pages_per_area, in debug_areas_alloc()
204 if (!areas[i]) in debug_areas_alloc()
207 areas[i][j] = kzalloc(PAGE_SIZE, GFP_KERNEL); in debug_areas_alloc()
208 if (!areas[i][j]) { in debug_areas_alloc()
210 kfree(areas[i][j]); in debug_areas_alloc()
211 kfree(areas[i]); in debug_areas_alloc()
216 return areas; in debug_areas_alloc()
[all …]
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | pixfmt-meta-vsp1-hgt.rst | 32 between 1 and 16 depending on the Hue areas configuration. Finding the
41 how the HGT Hue areas are configured. There are 6 user configurable Hue
65 When two consecutive areas don't overlap (n+1L is equal to nU) the boundary
70 with a hue value included in the overlapping region between two areas (between
71 n+1L and nU excluded) are attributed to both areas and given a weight for each
72 of these areas proportional to their position along the diagonal lines
|
| /Linux-v5.4/Documentation/devicetree/bindings/gpu/ |
| D | brcm,bcm-v3d.txt | 8 - reg: Physical base addresses and lengths of the register areas
9 - reg-names: Names for the register areas. The "hub" and "core0"
10 register areas are always required. The "gca" register area
|
| /Linux-v5.4/drivers/soc/renesas/ |
| D | rcar-sysc.h | 45 const struct rcar_sysc_area *areas; member
72 extern void rcar_sysc_nullify(struct rcar_sysc_area *areas,
|
| D | rcar-sysc.c | 374 const struct rcar_sysc_area *area = &info->areas[i]; in rcar_sysc_pd_init()
421 void __init rcar_sysc_nullify(struct rcar_sysc_area *areas, in rcar_sysc_nullify() argument
427 if (areas[i].isr_bit == id) { in rcar_sysc_nullify()
428 areas[i].name = NULL; in rcar_sysc_nullify()
|
| D | r8a77995-sysc.c | 25 .areas = r8a77995_areas,
|
| D | r8a7743-sysc.c | 27 .areas = r8a7743_areas,
|
| D | r8a7745-sysc.c | 27 .areas = r8a7745_areas,
|
| D | r8a77470-sysc.c | 27 .areas = r8a77470_areas,
|
| D | r8a7791-sysc.c | 28 .areas = r8a7791_areas,
|
| D | r8a7792-sysc.c | 29 .areas = r8a7792_areas,
|
| D | r8a7794-sysc.c | 28 .areas = r8a7794_areas,
|
| D | r8a7779-sysc.c | 29 .areas = r8a7779_areas,
|
| D | r8a77965-sysc.c | 34 .areas = r8a77965_areas,
|
| D | r8a77970-sysc.c | 33 .areas = r8a77970_areas,
|
| D | r8a774a1-sysc.c | 43 .areas = r8a774a1_areas,
|
| D | r8a7790-sysc.c | 43 .areas = r8a7790_areas,
|
| D | r8a774c0-sysc.c | 51 .areas = r8a774c0_areas,
|
| D | r8a7796-sysc.c | 43 .areas = r8a7796_areas,
|
| D | r8a77990-sysc.c | 51 .areas = r8a77990_areas,
|
| /Linux-v5.4/Documentation/s390/ |
| D | s390dbf.rst | 28 debug log for the caller. For each debug log exists a number of debug areas
30 pages in memory. In the debug areas there are stored debug entries (log records)
44 The debug areas themselves are also ordered in form of a ring buffer.
142 /* register 4 debug areas with one page each and 4 byte data field */
176 /* register 4 debug areas with one page each and data field for */
231 Flushing debug areas
233 Debug areas can be flushed with piping the number of the desired
234 area (0...n) to the debugfs file "flush". When using "-" all debug areas
243 2. Flush all debug areas::
247 Changing the size of debug areas
[all …]
|
| /Linux-v5.4/Documentation/admin-guide/mm/ |
| D | cma_debugfs.rst | 6 different CMA areas and to test allocation/release in each of the areas.
|
| D | ksm.rst | 19 The KSM daemon ksmd periodically scans those areas of user memory
35 KSM only operates on those areas of address space which an application
64 Like other madvise calls, they are intended for use on mapped areas of
66 includes unmapped gaps (though working on the intervening mapped areas),
70 restricting its use to areas likely to benefit. KSM's scans may use a lot
114 leave mergeable areas registered for next run.
171 how many times all mergeable areas have been scanned
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | sysfs-devices-platform-docg3 | 7 keylocked. Each docg3 chip (or floor) has 2 protection areas,
22 (0 or 1). Each docg3 chip (or floor) has 2 protection areas,
|
| /Linux-v5.4/Documentation/devicetree/bindings/mtd/ |
| D | stm32-fmc2-nand.txt | 7 - reg: NAND flash controller memory areas.
11 Regions 5 to 7 contain the same areas for CS1.
|
123456
