Post #1275660
2026-04-07 08:01 UTC
@Ronflaix ehh, well, there's a lot of interrupts, but generally speaking, it's not too bad. the CPU is suuper fast, you have lots of time to do most things (as long as you don't do soft-float calculations :P).
If you were really strapped for CPU time, I guess the routines could also be optimized a bunch. The audio samples and the big PWM lookup table are all just stored in the code right now, which I'm guessing will load them into the CPU d-cache at every firing of the interrupt.
Replies (1)
-
@manawyrm@chaos.social 2026-04-07 08:01
@Ronflaix In other words, every few milliseconds your actual main loop will get interrupted, the cache will be overwritten with audio data and then it'll return execution. That could (and maybe should?) be benchmarked and probably fixed :)