bbulkow/FastLED-idf
1
0
Fork 1
mirror of https://github.com/bbulkow/FastLED-idf.git synced 2025-07-29 18:28:23 +02:00
Code Issues Packages Projects Releases Wiki Activity

Updated documentation about parallel use

Browse Source
This commit is contained in:
Brian Bulkowski
2020-03-01 14:45:36 -08:00
parent 4792d6cbe8
commit 17bffd84e6
2 changed files with 9 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -163,6 +163,10 @@ the pod bay doors.
On an ESP32 running at 240Mhz, I was able to time 40 pixels at 1.2 milliseconds. I timed showLeds()
at 3.0 milliseconds at 100 LEDs.
However, if you use more than one controller ( see the THREADING document ),
three different controllers each will do 100 LEDs in 3 milliseconds. I have tested
this with 1, 3, and 6 controllers. They all take the same amount of time.
If 30 milliseconds makes 30fps, then you should be able to do 1000 pixels on one of the two cores,
and still, potentially, have the ability to do some extra work, because you've got the other CPU.

7
THREADING.md
View File

@ -16,9 +16,12 @@ for this platform --- and it's a little weird.
For this platform, when you do a showLeds(), it keeps track of the number
of calls, and when you reach the same number of calls as the number of allocated
controllers, it actually spins up all of them together.
controllers, it actually spins up all of them together. I believe
this is intended to work because showLeds() will call each
of them in turn, so you use that.
To say that's "peculiar" stretches the point.
I worry if you try to call the showLeds on individual controllers
and hope the right thing happens.
You'd prefer an interface called something like "flushLeds" which
acts on all the known controllers, or takes the list of controllers