Home
last modified time | relevance | path

Searched refs:areas (Results 1 – 25 of 157) sorted by relevance

1234567

/kernel/linux/linux-5.10/arch/s390/kernel/
Ddebug.c181 debug_entry_t ***areas; in debug_areas_alloc() local
184 areas = kmalloc_array(nr_areas, sizeof(debug_entry_t **), GFP_KERNEL); in debug_areas_alloc()
185 if (!areas) in debug_areas_alloc()
189 areas[i] = kmalloc_array(pages_per_area, in debug_areas_alloc()
192 if (!areas[i]) in debug_areas_alloc()
195 areas[i][j] = kzalloc(PAGE_SIZE, GFP_KERNEL); in debug_areas_alloc()
196 if (!areas[i][j]) { in debug_areas_alloc()
198 kfree(areas[i][j]); in debug_areas_alloc()
199 kfree(areas[i]); in debug_areas_alloc()
204 return areas; in debug_areas_alloc()
[all …]
/kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/
Dpixfmt-meta-vsp1-hgt.rst25 between 1 and 16 depending on the Hue areas configuration. Finding the
34 how the HGT Hue areas are configured. There are 6 user configurable Hue
58 When two consecutive areas don't overlap (n+1L is equal to nU) the boundary
63 with a hue value included in the overlapping region between two areas (between
64 n+1L and nU excluded) are attributed to both areas and given a weight for each
65 of these areas proportional to their position along the diagonal lines
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/gpu/
Dbrcm,bcm-v3d.txt8 - 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
/kernel/linux/linux-5.10/drivers/soc/renesas/
Dr8a7796-sysc.c46 .areas = r8a7796_areas,
62 .areas = r8a7796_areas,
Drcar-sysc.h45 const struct rcar_sysc_area *areas; member
79 extern void rcar_sysc_nullify(struct rcar_sysc_area *areas,
Drcar-sysc.c402 const struct rcar_sysc_area *area = &info->areas[i]; in rcar_sysc_pd_init()
449 void __init rcar_sysc_nullify(struct rcar_sysc_area *areas, in rcar_sysc_nullify() argument
455 if (areas[i].isr_bit == id) { in rcar_sysc_nullify()
456 areas[i].name = NULL; in rcar_sysc_nullify()
Dr8a77995-sysc.c24 .areas = r8a77995_areas,
Dr8a7743-sysc.c26 .areas = r8a7743_areas,
Dr8a7745-sysc.c26 .areas = r8a7745_areas,
Dr8a77470-sysc.c26 .areas = r8a77470_areas,
Dr8a7791-sysc.c27 .areas = r8a7791_areas,
Dr8a7794-sysc.c27 .areas = r8a7794_areas,
Dr8a7792-sysc.c28 .areas = r8a7792_areas,
Dr8a7779-sysc.c28 .areas = r8a7779_areas,
Dr8a774b1-sysc.c33 .areas = r8a774b1_areas,
Dr8a77965-sysc.c34 .areas = r8a77965_areas,
Dr8a77970-sysc.c33 .areas = r8a77970_areas,
Dr8a7742-sysc.c40 .areas = r8a7742_areas,
Dr8a774a1-sysc.c42 .areas = r8a774a1_areas,
Dr8a7790-sysc.c42 .areas = r8a7790_areas,
Dr8a774c0-sysc.c51 .areas = r8a774c0_areas,
/kernel/linux/linux-5.10/Documentation/s390/
Ds390dbf.rst28 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.
140 /* register 4 debug areas with one page each and 4 byte data field */
173 /* register 4 debug areas with one page each and data field for */
228 Flushing debug areas
230 Debug areas can be flushed with piping the number of the desired
231 area (0...n) to the debugfs file "flush". When using "-" all debug areas
240 2. Flush all debug areas::
244 Changing the size of debug areas
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/mm/
Dcma_debugfs.rst6 different CMA areas and to test allocation/release in each of the areas.
Dksm.rst19 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
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-devices-platform-docg37 keylocked. Each docg3 chip (or floor) has 2 protection areas,
24 (0 or 1). Each docg3 chip (or floor) has 2 protection areas,

1234567