You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
west build samples/drivers/display -b xiao_esp32s3/esp32s3/procpu/sense
Set CONFIG_DMA=y in Kconfig
Expected behavior
Coloured squares drawn in screen corners as per the sample
Impact
Poor performance using displays in LVGL, due to lack of DMA
Environment (please complete the following information):
OS: Linux
Toolchain: Zephyr SDK
Commit SHA or Version used: ad431b3 (latest main, as of writing this issue)
Additional Context
I ran the spi_loopback test using DMA on this board, and initially I had problems (#87127) until I enabled CONFIG_CLOCK_CONTROL which seems to be required for SPI-via-DMA to work (but it -should- be selected automatically in all cases for esp32s3).
Sadly, enabling it did not fix THIS issue.
The text was updated successfully, but these errors were encountered:
Describe the bug
Similar to #82095 (but the workaround for that issue is not applicable to esp32, since esp32 arch apparently does not have support for NOCACHE memory)
No output on screen or console if DMA is enabled
To Reproduce
Enable DMA by setting dma-enabled in the SPI device node, setting status okay in the DMA node, and setting CONFIG_DMA=y
(I am using the following devicetree for xiao_esp32s3/esp32s3/procpu/sense)
samples/drivers/display/xiao_esp32s3_esp32s3_procpu_sense.overlay
west build samples/drivers/display -b xiao_esp32s3/esp32s3/procpu/sense
Set CONFIG_DMA=y in Kconfig
Expected behavior
Coloured squares drawn in screen corners as per the sample
Impact
Poor performance using displays in LVGL, due to lack of DMA
Environment (please complete the following information):
Additional Context
I ran the
spi_loopback
test using DMA on this board, and initially I had problems (#87127) until I enabledCONFIG_CLOCK_CONTROL
which seems to be required for SPI-via-DMA to work (but it -should- be selected automatically in all cases for esp32s3).Sadly, enabling it did not fix THIS issue.
The text was updated successfully, but these errors were encountered: