Mahavir Jain aba35cd526 fix(aes): correct the linking of the DMA descriptors ... For certain data lengths, the last input descriptor was not getting appended correctly and hence the EOF flag in the DMA descriptor link list was set at incorrect location. This was resulting in the peripheral being stalled expecting more data and eventually the code used to timeout waiting for the AES completion interrupt. Required configs for this issue: CONFIG_MBEDTLS_HARDWARE_AES CONFIG_SOC_AES_SUPPORT_DMA This observation is similar to the issue reported in: https://github.com/espressif/esp-idf/issues/10647 To recreate this issue, start the AES-GCM DMA operation with data length 12280 bytes and this should stall the operation forever. In this fix, we are tracing the entire descriptor list and then appending the extra bytes descriptor at correct position (as the last node).		2023-09-06 08:30:00 +05:30
..
include	aes/sha: use a shared lazy allocated GDMA channel for AES and SHA	2021-03-09 09:23:05 +08:00
esp_aes_crypto_dma_impl.c	AES/SHA: use GDMA driver instead of LL	2021-01-19 11:02:51 +08:00
esp_aes_gdma_impl.c	aes/sha: use a shared lazy allocated GDMA channel for AES and SHA	2021-03-09 09:23:05 +08:00
esp_aes.c	fix(aes): correct the linking of the DMA descriptors	2023-09-06 08:30:00 +05:30