> On Nov 4, 2015, at 12:30 PM, Sterling Hughes <[email protected]> wrote: > > I think this is documentation. You may want it to be the highest > priority task, but what if somebody has two interfaces, and doesn't > care if they miss packets or data on the BLE link? > > I think it should just be clearly spelled out in documentation that > it's a good thing for BLE to be highest priority task, and the latency > requirement from when an interrupt occurs to when the task is swapped > in (and count a statistic/log a message when that happens.) >
I agree it’s best to have the priority defined by project, and passing that as argument is a fine way of doing that. I like it better than having them defined in header file. And have hints about relative priority of tasks somewhere. Either in documentation and/or sample code which uses that subsystem.
