esp-idf/components/esp_mm
Mahavir Jain deab1da6f2 fix(esp_mm): for existing mmap region, consider new offset for virtual addr
While returning virtual address for existing memory mapped region, newly
supplied offset from the physical address was not getting considered.

This was a regression present from ESP-IDF 5.1 release.

Added test case in spi_flash component that fails without this fix.

Closes https://github.com/espressif/esp-idf/issues/13929
2024-07-15 12:42:45 +08:00
..
include fix(esp_mm): for existing mmap region, consider new offset for virtual addr 2024-07-15 12:42:45 +08:00
port esp32h4: remove esp32h4 target from peripherals 2023-04-26 18:53:10 +08:00
test_apps ci: remove redundent ci configs for chip support and network components 2023-04-26 17:29:51 +08:00
cache_esp32.c esp_mm: fix dependency to esp_psram 2023-02-28 10:42:22 +08:00
CMakeLists.txt esp_mm: cache_msync API 2023-02-28 10:42:22 +08:00
esp_cache.c fix(cache): no longer use freeze in esp_cache_msync 2023-07-21 17:19:11 +08:00
esp_mmu_map.c fix(esp_mm): for existing mmap region, consider new offset for virtual addr 2024-07-15 12:42:45 +08:00
ext_mem_layout.h esp_mm: new virtual memory mapping apis via mmu 2023-02-07 20:23:52 +08:00
linker.lf esp_mm: fix dependency to esp_psram 2023-02-28 10:42:22 +08:00