| commit | 9ea45b7c37901c4c4ef943f2335b85262bf60c1d | |
| author | Dominic Clifton <dominic.clifton@cleanflight.com> | |
| Mon, 7 Mar 2022 14:41:20 +0000 (7 15:41 +0100) | ||
| committer | Dominic Clifton <dominic.clifton@cleanflight.com> | |
| Wed, 16 Mar 2022 12:47:58 +0000 (16 13:47 +0100) | ||
| tree | 3f5d5f42b309f392ac95cfb468ad69fa614acf44 | treesnapshot (tar.gz zip) |
| parent | d653dabebb37f550dcacc607e2c9f10c5f2268c9 | commitdiff |
NVIC - Remove outdated comment.
Yes, there is a reason to use DMAIRQHandler, so that the WS2811 dma
transfer complete handler can update the ws2811LedDataTransferInProgress
flag.
Potentially though the timer could be left running and restarted when
the next led strip update occurs and the dma transfer 'numbers of bytes
to transfer' field could be read instead of the
ws2811LedDataTransferInProgress flag...
Yes, there is a reason to use DMAIRQHandler, so that the WS2811 dma
transfer complete handler can update the ws2811LedDataTransferInProgress
flag.
Potentially though the timer could be left running and restarted when
the next led strip update occurs and the dma transfer 'numbers of bytes
to transfer' field could be read instead of the
ws2811LedDataTransferInProgress flag...
| src/main/drivers/nvic.h | diffblobblamehistory |