Home
last modified time | relevance | path

Searched full:mappings (Results 1 – 25 of 109) sorted by relevance

12345

/Zephyr-latest/doc/kernel/memory_management/
Dvirtual_memory.rst59 * :kconfig:option:`CONFIG_KERNEL_DIRECT_MAP`: permits 1:1 mappings between
89 |..............| <- grows downward as more mappings are made
97 +--------------+ <- memory mappings start here
133 Virtual Memory Mappings
136 Setting up Mappings at Boot argument
139 In general, most supported architectures set up the memory mappings at boot as
159 Caching modes for these mappings are architecture specific. They can be
162 Note that SoCs have their own additional mappings required to boot where
163 these mappings are defined under their own SoC configurations. These mappings
172 mappings must be aligned on page size and have finer access control.
/Zephyr-latest/kernel/
DKconfig.vm43 mappings (with potentially different permissions).
73 size of the virtual region for runtime memory mappings. This is needed
76 mappings. The kernel itself will be mapped in here as well at boot.
91 there isn't overlap with the existed mappings, it will reserve the
127 bool "Allow on-demand memory mappings"
131 When this is enabled, RAM-based memory mappings don't actually
159 all page frames via anonymous memory mappings.
/Zephyr-latest/include/zephyr/kernel/internal/
Dmm.h103 "address %p not in permanent mappings", virt); in k_mem_phys_addr()
115 "address %p not in permanent mappings", virt); in k_mem_phys_addr()
210 * frames. It may conflict with anonymous memory mappings and demand paging
231 * where temporary memory mappings need to be made. This allows these
232 * memory mappings to be discarded once they are no longer needed.
243 * It is highly discouraged to use this function to unmap memory mappings.
244 * It may conflict with anonymous memory mappings and demand paging and
309 * This removes the memory mappings for the provided page-aligned region,
/Zephyr-latest/arch/xtensa/core/
DREADME_MMU.txt15 "special" ways storing mappings under OS control. Some of these are
162 top-level "L1" page containing the mappings for the page table
181 double mappings.
200 unchangable mappings from the final 384M of memory to the bottom and
203 remaining memory space would be used for virtual mappings. This
215 data, and leave any existing mappings in place in the TLB using the
234 Note, obviously, that any change of the mappings within an ASID
262 notifying another CPU of changes to page mappings beyond doing
267 page table mappings in the system are set uncached. The OS makes no
/Zephyr-latest/doc/hardware/arch/
Dx86.rst76 Specifying Additional Memory Mappings at Build Time
83 memory mappings. This is useful for static mappings and/or device MMIO
118 Note that specifying additional memory mappings requires larger storage
/Zephyr-latest/dts/bindings/arm/
Dnxp,mcux-xbar.yaml17 Crossbar input and output mappings. Input is followed by the output.
/Zephyr-latest/scripts/logging/dictionary/dictionary_parser/
Dlog_database.py170 """Get string mappings to database"""
175 """Add string mappings to database"""
180 """Return True if there are string mappings in database"""
279 # JSON encodes the addresses in string mappings as literal strings.
/Zephyr-latest/soc/mediatek/mt8xxx/
Dmtk_adsp_load.py39 # Runtime mmap objects for each MAPPINGS entry
52 # Parse devicetree to find the MMIO mappings: there is an "adsp" node
53 # (in various locations) with an array of named "reg" mappings. It
59 def mappings(): function
226 mmio = mappings()
228 # Open device and establish mappings
/Zephyr-latest/kernel/include/
Dmmu.h55 * @brief Get physical address from virtual address for boot RAM mappings.
57 * @note Only applies to boot RAM mappings within the Zephyr image that have never
68 * @brief Get virtual address from physical address for boot RAM mappings.
70 * @note Only applies to boot RAM mappings within the Zephyr image that have never
121 * anonymous mappings. We don't currently maintain an ontology of these in the
366 * marked as available for mappings or page-ins.
/Zephyr-latest/dts/bindings/led_strip/
Dti,tlc5971.yaml12 The color order of the TLC5971 is BGR. Applications can provide custom mappings
/Zephyr-latest/include/zephyr/arch/arm/mmu/
Darm_mmu.h53 * for the specification of mappings whose PA and VA differ,
55 * mapping, which are used for the mappings of the Zephyr image's
/Zephyr-latest/snippets/xen_dom0/boards/
Dqemu_cortex_a53.overlay35 * (XEN) Allocating 1:1 mappings for dom0:
Drcar_h3ulcb_r8a77951_a57.overlay31 * (XEN) Allocating 1:1 mappings for dom0:
Drcar_salvator_xs.overlay31 * (XEN) Allocating 1:1 mappings for dom0:
Drcar_spider_s4_r8a779f0_a55.overlay33 * (XEN) Allocating 1:1 mappings for dom0:
/Zephyr-latest/samples/drivers/led/lp5562/
DREADME.rst28 mappings used by this sample.
/Zephyr-latest/include/zephyr/xen/public/
Dgrant_table.h162 * @trans_grant in @trans_domid. No mappings are allowed.
172 * GTF_readonly: Restrict @domid to read-only mappings and accesses. [GST]
177 * mappings of the grant [GST]
262 * 3. Mappings should only be destroyed via GNTTABOP_unmap_grant_ref. If a
281 * GNTTABOP_unmap_grant_ref: Destroy one or more grant-reference mappings
289 * mappings will remain in the device or host TLBs.
/Zephyr-latest/include/zephyr/drivers/mm/
Dmm_drv_intel_adsp_mtl_tlb.h37 * and recreate physical to virtual mappings
/Zephyr-latest/doc/connectivity/networking/api/
Dtraffic-class.rst26 See :zephyr_file:`subsys/net/ip/net_tc.c` for details of how various mappings are done.
/Zephyr-latest/boards/adafruit/nrf52_adafruit_feather/
Dboard.h10 /* External edge connector pin mappings to nRF52 GPIO pin numbers.
/Zephyr-latest/dts/bindings/i2c/
Dinfineon,xmc4xxx-i2c.yaml63 Refer to the XMC4XXX reference manual for the GPIO pin/mux mappings.
79 Refer to the XMC4XXX reference manual for the GPIO pin/mux mappings.
/Zephyr-latest/boards/bbc/microbit/
Dboard.h10 /* External edge connector pin mappings to nRF51 GPIO pin numbers.
/Zephyr-latest/scripts/ci/
Dupload_test_results_es.py256 mappings = {}
260 mappings = json.load(json_map)
262 mappings = {
285 es.indices.create(index=args.index, mappings=mappings, settings=settings)
/Zephyr-latest/soc/nxp/imxrt/imxrt11xx/
Dpower.c31 /* Configure the set point mappings for Cortex M4 and M7 cores */
44 /* Cortex Set point mappings */ in gpc_set_core_mappings()
190 /* Setup GPC set point mappings */ in gpc_init()
/Zephyr-latest/drivers/mbox/
Dmbox_nrf_bellboard_rx.c20 "# interrupt mappings not specified in pairs");
22 /* BELLBOARD event mappings */

12345