dakejahl commented on issue #16373: URL: https://github.com/apache/nuttx/issues/16373#issuecomment-2893017296
Thanks for the reply! Okay yeah that makes sense. Using signals makes sense, there's a sem already in use for the STM32H7 SPI RX complete. Unfortunately I'm dealing with a pre-compiled library + API that imposes tight timing requirements, a supplied callback must be invoked <60us after the last SPI TX frame (before the DRDY fires and calls another callback, and the order of callbacks matters). I temporarily solved the issue by increasing the thread priority of my driver such that it's not pre-empted between SPI_EXCHANGE and callback() and instead benefits from pre-emption once the SPI_EXCHANGE is complete. It's not ideal since the driver shouldn't actually be high priority. I'll have to think about this harder. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
