FelipeMdeO commented on issue #13855: URL: https://github.com/apache/nuttx/issues/13855#issuecomment-2444970936
Hello @xiaoxiang781216 , don't you think it would be better for us to discuss this behavior a little more? Perhaps the driver should be changed, as it is expected that the same application behaves consistently across different drivers. What I mean is that an application running on an ST [likely referring to STMicroelectronics or a specific ST platform] won't need to handle receiving "garbage" from the lower half due to a specific behavior of Espressif. Therefore, if it becomes necessary to migrate an app running on ST to Espressif, it would be necessary to modify the application. @eren-terzioglu , looking at the following excerpt from the documentation: "Every clock pulse, a data bit is shifted from the Host to the Device on the MOSI line and back on the MISO line at the same time." I understand that a bit is sent from the host to the device and at the same instant a bit from the device is sent to the host, but not exactly the same bit. In fact, we do not see exactly the same bit being sent; we see the corresponding bit from the previous transaction. But it can be a misunderstand from my side. I believe @Donny9 could give us his opinion on this. If we come to the understanding that the driver's behavior should not send anything when nothing is requested by the app, we should enforce this in the lower half (which is exactly what I have been doing currently in the solution I am working on). -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
