jlaitine commented on PR #17221: URL: https://github.com/apache/nuttx/pull/17221#issuecomment-3460377264
> > Just please verify that 1) the udelay busyloops only appriximately the correct time and 2) tick based timeouts don't randomly timeout too early. These would be fatal bugs, and were the reasons why all those previous fixes were done. > > Otherwise, I don't have a religion on this; I am just tired of debugging issues caused by misbehaving basic timers... > > Okay, in that case I will mark this as a draft PR so merging can be held until I have some proper verification that the reverted commit won't cause timeouts to happen too early. @jlaitine would you want to see some kind of empirical test on multiple architectures, or just some empirical test on the simulator + logical verification that this 'accurate' method can never time out too early? I am not as well-versed on the systick drift issue as you would be, I'm sure. If you have any pointers to where to look for the underlying reason of the systick drift, I'm all ears. I figured the system tick wouldn't have such an issue but I guess that was naive. I'll try to do my best to help in testing. For the previous realted PRs I did some simple tests, I'll try to find and gather them and try this PR out on some risc-v and arm64 targets at least (as those are the most important for me at the time being) - and report how it behaves. It will take a day or two before I can put effort in this, as I am currently in the middle of something else. Anyhow, I'll try to be more helpful in the future. -- 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]
