tinnedkarma commented on issue #17004: URL: https://github.com/apache/nuttx/issues/17004#issuecomment-3287888639
> [@tinnedkarma](https://github.com/tinnedkarma) `CONFIG_BOARD_LOOPSPERMSEC` depends heavily on configuration options such as optimization level, support for vector operations or even the compiler used. The value of this option will be completely different for optimization disabled and full optimization enabled. This can't be per-board configuration, it must be per-config configuration. Unfortunately, it is not very user-friendly and is prone to errors that are difficult to find later (timings errors!). > For targets without memory restrictions and that don't care about boot time, we can calibrate busy delays at system startup, as Linux does. However, this isn't a universal solution, as there are many embedded applications where this isn't acceptable. This makes sense. I am more than comfortable having it as a kconfig option. Also, I fully agree that there is no universal solution, the good solution is what we agree upon. I just presented a different view for the same problem. -- 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
