Only SPI. I don't want to pause DMA, it should do the transfer when requested, but not generate interrupt on completion. The thing is I'm using LCD interrupts as well, and I don't know how to change interrupt priorities of any of them, so I guess that increasing priority of LCD interrupt would also ...

Thank you for your reply. The thing is that I don't want interrupt on any of the cores. I was hoping that it's possible to check if there is a flag indicating that SPI message is received. Then I would clear the "flag", process the received message and initiate another SPI transfer manually.

At the moment I'm initializing SPI slave to use a callback function when SPI transfer is finished and it works fine, except for the fact that it sometimes occurres in inconvenient times. Because of that, I would prefer to check myself if the transfer is finished and then do the appropriate tasks. My ...

Thanks for your reply.
I would prefer to have a hardware timer, but if nobody offers a different solution, I'll have to use them.

I used all 4 timers on my ESP32-S3 project and I found out I'll need some more. I previously worked on some other MCU that had a similar number of timers, but had a MCP module that had it's own timers that were available. I can see that ESP32-S3 also has MCPWM module with timers so I was wondering ...

I have two ESP32-S3s connected to each other and I'm trying to send data from one to the other. I have verified with the oscilloscope that the master side is sending the data correctly on all four data lines and SCK/CS. After that I configured the slave like this:

typedef struct SPI_settings_s ...

I was hoping for 40Mhz, so yes, 16MHz is a bare minimum.

It's ok, found it, gpio_set_drive_capability. It helped a bit.

How can I do that?

OK, I've shortened the length of wires by half and now it looks better. Still far from perfect, but I guess it will be fine when all components are on one PCB.
If anybody have any suggestions on still improving the signal, it would be much appreciated.