Home
last modified time | relevance | path

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

1234567

/linux/arch/s390/kernel/
A Ddebug.c185 if (!areas) in debug_areas_alloc()
192 if (!areas[i]) in debug_areas_alloc()
204 return areas; in debug_areas_alloc()
210 kfree(areas[i]); in debug_areas_alloc()
212 kfree(areas); in debug_areas_alloc()
239 if (!rc->areas) in debug_info_alloc()
242 rc->areas = NULL; in debug_info_alloc()
353 memcpy(rc->areas[i][j], in->areas[i][j], PAGE_SIZE); in debug_info_copy()
430 if (!id->areas) in debug_next_entry()
891 swap(a->areas, b->areas); in debug_areas_swap()
[all …]
/linux/Documentation/userspace-api/media/v4l/
A 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
/linux/arch/s390/include/asm/
A Ddebug.h54 debug_entry_t ***areas; member
424 static debug_entry_t **VNAME(var, areas)[EARLY_AREAS] __initdata = { \
440 .areas = VNAME(var, areas), \
451 #define __REGISTER_STATIC_DEBUG_INFO(var, name, pages, areas, view) \ argument
454 debug_register_static(&var, (pages), (areas)); \
/linux/Documentation/s390/
A Ds390dbf.rst28 debug log for the caller. For each debug log exists a number of debug areas
44 The debug areas themselves are also ordered in form of a ring buffer.
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
240 2. Flush all debug areas::
244 Changing the size of debug areas
246 It is possible the change the size of debug areas through piping
248 also flush the debug areas.
252 Define 4 pages for the debug areas of debug feature "dasd"::
[all …]
/linux/drivers/soc/renesas/
A Dr8a7796-sysc.c46 .areas = r8a7796_areas,
62 .areas = r8a7796_areas,
A Drcar-sysc.h45 const struct rcar_sysc_area *areas; member
79 extern void rcar_sysc_nullify(struct rcar_sysc_area *areas,
A Drcar-sysc.c397 const struct rcar_sysc_area *area = &info->areas[i]; in rcar_sysc_pd_init()
448 void __init rcar_sysc_nullify(struct rcar_sysc_area *areas, in rcar_sysc_nullify() argument
454 if (areas[i].isr_bit == id) { in rcar_sysc_nullify()
455 areas[i].name = NULL; in rcar_sysc_nullify()
A Dr8a779a0-sysc.c48 const struct r8a779a0_sysc_area *areas; member
100 .areas = r8a779a0_areas,
405 const struct r8a779a0_sysc_area *area = &info->areas[i]; in r8a779a0_sysc_pd_init()
A Dr8a77995-sysc.c24 .areas = r8a77995_areas,
A Dr8a7743-sysc.c26 .areas = r8a7743_areas,
A Dr8a7745-sysc.c26 .areas = r8a7745_areas,
A Dr8a77470-sysc.c26 .areas = r8a77470_areas,
A Dr8a7791-sysc.c27 .areas = r8a7791_areas,
A Dr8a7792-sysc.c28 .areas = r8a7792_areas,
A Dr8a7794-sysc.c27 .areas = r8a7794_areas,
A Dr8a7779-sysc.c28 .areas = r8a7779_areas,
A Dr8a774b1-sysc.c33 .areas = r8a774b1_areas,
A Dr8a77965-sysc.c34 .areas = r8a77965_areas,
A Dr8a77970-sysc.c33 .areas = r8a77970_areas,
A Dr8a7742-sysc.c40 .areas = r8a7742_areas,
/linux/Documentation/admin-guide/mm/
A 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
A Dcma_debugfs.rst6 different CMA areas and to test allocation/release in each of the areas.
/linux/Documentation/ABI/testing/
A 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,
/linux/Documentation/devicetree/bindings/net/
A Dcortina,gemini-ethernet.txt11 memory areas, in total three register sets.
28 - reg: must contain two register areas: the DMA/TOE memory and
/linux/Documentation/userspace-api/accelerators/
A Docxl.rst66 work with, the size of its MMIO areas, ...
73 OpenCAPI defines two MMIO areas for each AFU:
158 MMIO areas, the AFU version, and the PASID for the current context.

Completed in 35 milliseconds

1234567