b2dd038814
In the entire code base, we basically use 4 LED scenarios: - all off - active slot green on - active slot green blinking - active slot red blinking Compacting this behaviour into 4 functions saves in total ~140B - which is huge. It's not an entirely clean solution, LEDs should not know anything about globals::ActiveSlot, but the savings are more important. Ideally, such an optimization could have been done by the compiler. |
||
|---|---|---|
| .. | ||
| buttons | ||
| leds | ||
| motion | ||
| protocol | ||
| pulse_gen | ||
| speed_table | ||
| stubs | ||
| timebase | ||
| user_input | ||
| CMakeLists.txt | ||