Replies: 4 comments 1 reply
-
|
It seems that this commit breaks asynchronous api. When using zephyr 4.0.0 there is no problem and async api do not block execution. In zephyr 4.1.0 async api block execution. And probably the issue does not affect only slave mode, but master mode also. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @mczerski I know this is bit old but did you get to the bottom of how to fix this behaviour? Cheers Andy |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for the (very) late reply, I have an on-going PR that should fix this: #103079, especially commit 9ad6e7a |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the info, no need to be sorry :) |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone,
I don't know if it is a bug in STM32 SPI driver or I am missing something.
Does the spi_transceive_cb function should block ?
I have CONFIG_SPI_SLAVE=y and CONFIG_SPI_ASYNC=y, and example code below that blocks the main thread until first byte is received by the SPI peripheral. The call to spi_transceive_cb blocks in spi_ll_stm32.c in while loop
while (!ret && spi_stm32_transfer_ongoing(data));. For me it looks like the driver does not support asynchronous mode properly.Beta Was this translation helpful? Give feedback.
All reactions