Searched full:mapping (Results 1 – 25 of 457) sorted by relevance
12345678910>>...19
| /Documentation/ |
| D | io-mapping.txt | 8 The io_mapping functions in linux/io-mapping.h provide an abstraction for
9 efficiently mapping small regions of an I/O device to the CPU. The initial
14 A mapping object is created during driver initialization using::
20 mappable, while 'size' indicates how large a mapping region to
23 This _wc variant provides a mapping which may only be used
26 With this mapping object, individual pages can be mapped either atomically
30 void *io_mapping_map_atomic_wc(struct io_mapping *mapping,
33 'offset' is the offset within the defined mapping region.
59 void *io_mapping_map_wc(struct io_mapping *mapping,
75 void io_mapping_free(struct io_mapping *mapping)
[all …]
|
| D | nommu-mmap.txt | 2 No-MMU memory mapping support
5 The kernel has limited support for memory mapping under no-MMU conditions, such
7 mapping is made use of in conjunction with the mmap() system call, the shmat()
9 mapping is actually performed by the binfmt drivers, which call back into the
12 Memory mapping behaviour also involves the way fork(), vfork(), clone() and
19 (#) Anonymous mapping, MAP_PRIVATE
27 (#) Anonymous mapping, MAP_SHARED
37 the underlying file are reflected in the mapping; copied across fork.
41 - If one exists, the kernel will re-use an existing mapping to the
45 - If possible, the file mapping will be directly on the backing device
[all …]
|
| D | DMA-attributes.txt | 6 defined in linux/dma-mapping.h.
23 could race with data DMA. Mapping the memory used for completion
29 DMA_ATTR_WEAK_ORDERING specifies that reads and writes to the mapping
39 DMA_ATTR_WRITE_COMBINE specifies that writes to the mapping may be
58 virtual mapping for the allocated buffer. On some architectures creating
59 such mapping is non-trivial task and consumes very limited resources
78 having a mapping created separately for each device and is usually
93 device domain after releasing a mapping for it. Use this attribute with
99 By default DMA-mapping subsystem is allowed to assemble the buffer
108 This is a hint to the DMA-mapping subsystem that it's probably not worth
[all …]
|
| D | IRQ-domain.txt | 2 The irq_domain interrupt number mapping library
28 irq numbers, but they don't provide any support for reverse mapping of
32 The irq_domain library adds mapping between hwirq and IRQ numbers on
33 top of the irq_alloc_desc*() API. An irq_domain to manage mapping is
35 reverse mapping scheme.
45 calling one of the irq_domain_add_*() functions (each mapping method
53 hwirq number as arguments. If a mapping for the hwirq doesn't already
72 There are several mechanisms available for reverse mapping from hwirq
124 Very few drivers should need this mapping.
133 The No Map mapping is to be used when the hwirq number is
[all …]
|
| D | DMA-API-HOWTO.txt | 2 Dynamic DMA mapping Guide
53 | | mapping | | by host | |
59 | | Virtual |Buffer| Mapping | |
61 | | mapping | RAM | by IOMMU
86 mapping and returns the DMA address Z. The driver then tells the device to
90 So that Linux can use the dynamic DMA mapping, it needs some help from the
105 #include <linux/dma-mapping.h>
109 everywhere you hold a DMA address returned from the DMA mapping functions.
115 be used with the DMA mapping facilities. There has been an unwritten
337 The interfaces for using this type of mapping were designed in
[all …]
|
| /Documentation/xtensa/ |
| D | booting.rst | 14 the address must be a valid address in the current mapping. The kernel will
15 not change the mapping on its own.
17 default virtual mapping (0xd0000000..0xffffffff).
20 virtual mapping. It is considered physical if it is within the range of
21 physical addresses covered by the default KSEG mapping (XCHAL_KSEG_PADDR..
|
| /Documentation/devicetree/bindings/sound/ |
| D | st,sta32x.txt | 34 - st,ch1-output-mapping: Channel 1 output mapping
35 - st,ch2-output-mapping: Channel 2 output mapping
36 - st,ch3-output-mapping: Channel 3 output mapping
93 st,ch1-output-mapping = /bits/ 8 <0>; // set channel 1 output ch 1
94 st,ch2-output-mapping = /bits/ 8 <0>; // set channel 2 output ch 1
95 st,ch3-output-mapping = /bits/ 8 <0>; // set channel 3 output ch 1
|
| D | st,sta350.txt | 30 - st,ch1-output-mapping: Channel 1 output mapping
31 - st,ch2-output-mapping: Channel 2 output mapping
32 - st,ch3-output-mapping: Channel 3 output mapping
123 st,ch1-output-mapping = /bits/ 8 <0>; // set channel 1 output ch 1
124 st,ch2-output-mapping = /bits/ 8 <0>; // set channel 2 output ch 1
125 st,ch3-output-mapping = /bits/ 8 <0>; // set channel 3 output ch 1
|
| /Documentation/admin-guide/device-mapper/ |
| D | dm-zoned.rst | 66 mapping of the logical device blocks. The mapping is done per chunk of
68 mapping table is indexed by chunk number and each mapping entry
70 mapping entry may also indicate if the zone number of a conventional
74 blocks in the data zones follows the mapping table. A valid block is
76 data chunk, a block is always valid only in the data zone mapping the
80 are processed by directly writing to the zone. If the mapping zone is a
88 automatically invalidate the same block in the sequential zone mapping
90 is freed and the chunk buffer zone becomes the primary zone mapping the
96 the sequential zone mapping a chunk, or if the chunk is buffered, from
97 the buffer zone assigned. If the accessed chunk has no mapping, or the
[all …]
|
| /Documentation/arm/ |
| D | memory.rst | 26 setup a minicache mapping.
42 fffe8000 fffeffff DTCM mapping area for platforms with
45 fffe0000 fffe7fff ITCM mapping area for platforms with
48 ffc00000 ffefffff Fixmap mapping region. Addresses provided
51 fee00000 feffffff Mapping of PCI I/O space. This is a static
52 mapping within the vmalloc space.
68 One way of mapping HIGHMEM pages into kernel
83 space are also caught via this mapping.
90 Since future CPUs may impact the kernel mapping layout, user programs
|
| /Documentation/ia64/ |
| D | aliasing.rst | 30 page with both a cacheable mapping and an uncacheable mapping[1].
58 in the system because of constraints imposed by the identity mapping
72 identity mapping only when the entire granule supports cacheable
76 can referenced safely by an identity mapping.
102 by a kernel identity mapping, the user mapping must use the same
103 attribute as the kernel mapping.
105 If the region is not in kern_memmap, the user mapping should use
109 machines, this should use an uncacheable mapping as a fallback.
134 the WC mapping is allowed.
136 Otherwise, the user mapping must use the same attribute as the
[all …]
|
| /Documentation/vm/ |
| D | hugetlbfs_reserv.rst | 17 huge pages to cover the mapping, the mmap() would fail. This was first
19 were enough free huge pages to cover the mapping. Like most things in the
22 available for page faults in that mapping. The description below attempts to
52 There is one reserve map for each huge page mapping in the system.
54 the mapping. A region is described as::
63 indices into the mapping. Depending on the type of mapping, a
71 associated with the mapping.
73 Indicates task originally mapping this range (and creating
85 A huge page mapping or segment is either private or shared. If private,
93 time the mapping (mmap(MAP_PRIVATE)) is created.
[all …]
|
| D | remap_file_pages.rst | 7 The remap_file_pages() system call is used to create a nonlinear mapping,
8 that is, a mapping in which the pages of the file are mapped into a
14 Supporting of nonlinear mapping requires significant amount of non-trivial
16 nonlinear mapping work kernel need a way to distinguish normal page table
|
| D | page_migration.rst | 107 to access the page via the mapping to block on the spinlock.
124 11. The i_pages lock is dropped. With that lookups in the mapping
180 2. ``int (*migratepage) (struct address_space *mapping,``
211 void __SetPageMovable(struct page *page, struct address_space *mapping)
216 reuses page->mapping's lower bits to represent it.
220 page->mapping = page->mapping | PAGE_MAPPING_MOVABLE;
222 so driver shouldn't access page->mapping directly. Instead, driver should
223 use page_mapping which mask off the low two bits of page->mapping under
228 page->mapping field is unified with other variables in struct page.
229 As well, if driver releases the page after isolation by VM, page->mapping
[all …]
|
| D | highmem.rst | 20 The part of (physical) memory not covered by a permanent mapping is what we
55 * vmap(). This can be used to make a long duration mapping of multiple
59 * kmap(). This permits a short duration mapping of a single page. It needs
64 * kmap_atomic(). This permits a very short duration mapping of a single
65 page. Since the mapping is restricted to the CPU that issued it, it
84 struct page *page = find_get_page(mapping, offset);
116 If CONFIG_HIGHMEM is not set, then the kernel will try and create a mapping
132 pageframes need to live in the permanent mapping, which means:
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | cpus.txt | 24 - fsl,portid-mapping
27 Definition: The Coherency Subdomain ID Port Mapping Registers and
28 Snoop ID Port Mapping registers, which are part of the CoreNet
30 ID/CoreNet Snoop ID to cpu mapping functions. Certain bits from
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-backlight | 11 controls like sliders need to apply a logarithmic mapping for
21 controls should apply a logarithmic mapping for a linear
26 controls should use a linear mapping for a linear perception.
|
| /Documentation/devicetree/bindings/powerpc/4xx/ |
| D | ppc440spe-adma.txt | 16 - reg : <registers mapping>
35 - reg : <registers mapping>
37 - interrupts : <interrupt mapping for DMA0/1 interrupts sources:
65 - reg : <registers mapping>
66 - interrupts : <interrupt mapping for XOR interrupt source>
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | lm3630a-backlight.yaml | 76 ti,linear-mapping-mode:
78 Enable linear mapping mode. If disabled, then it will use exponential
79 mapping mode in which the ramp up/down appears to have a more uniform
127 ti,linear-mapping-mode;
133 ti,linear-mapping-mode;
|
| /Documentation/devicetree/bindings/display/panel/ |
| D | lvds.yaml | 41 data-mapping:
47 The color signals mapping order.
51 - "jeida-18" - 18-bit data mapping compatible with the [JEIDA], [LDI] and
62 - "jeida-24" - 24-bit data mapping compatible with the [DSIM] and [LDI]
74 - "vesa-24" - 24-bit data mapping compatible with the [VESA] specification.
101 - data-mapping
|
| /Documentation/x86/x86_64/ |
| D | mm.rst | 45 …ffff888000000000 | -119.5 TB | ffffc87fffffffff | 64 TB | direct mapping of all physical memory…
59 fffffe0000000000 | -2 TB | fffffe7fffffffff | 0.5 TB | cpu_entry_area mapping
63 ffffffef00000000 | -68 GB | fffffffeffffffff | 64 GB | EFI region mapping space
65 …ffffffff80000000 | -2 GB | ffffffff9fffffff | 512 MB | kernel text mapping, mapped to physic…
67 ffffffffa0000000 |-1536 MB | fffffffffeffffff | 1520 MB | module mapping space
104 …ff11000000000000 | -59.75 PB | ff90ffffffffffff | 32 PB | direct mapping of all physical memory…
118 fffffe0000000000 | -2 TB | fffffe7fffffffff | 0.5 TB | cpu_entry_area mapping
122 ffffffef00000000 | -68 GB | fffffffeffffffff | 64 GB | EFI region mapping space
124 …ffffffff80000000 | -2 GB | ffffffff9fffffff | 512 MB | kernel text mapping, mapped to physic…
126 ffffffffa0000000 |-1536 MB | fffffffffeffffff | 1520 MB | module mapping space
[all …]
|
| /Documentation/devicetree/bindings/rtc/ |
| D | google,goldfish-rtc.txt | 8 - reg : <registers mapping>
9 - interrupts : <interrupt mapping>
|
| /Documentation/devicetree/bindings/display/ |
| D | google,goldfish-fb.txt | 8 - reg : <registers mapping>
9 - interrupts : <interrupt mapping>
|
| /Documentation/devicetree/bindings/goldfish/ |
| D | audio.txt | 8 - reg : <registers mapping>
9 - interrupts : <interrupt mapping>
|
| D | tty.txt | 8 - reg : <registers mapping>
9 - interrupts : <interrupt mapping>
|
12345678910>>...19