Re: [riot-devel] Event driven drivers

2015-02-09 Thread Kaspar Schleiser
Hi Joakim, On 02/09/15 14:20, Joakim Gebart wrote: Has anyone measured the cost of the thread context switching on the different platforms? I'm mainly interested in Cortex-M4 (Kinetis). This would be a good indication of how slow an I/O device has to be before it is worth it to manually yield a

Re: [riot-devel] Event driven drivers

2015-02-09 Thread Hauke Petersen
Hi, we do indeed have a number of places in the driver code, where busy waiting is used. The reason for this is mostly missing man power to implement better versions of the same driver. The most important fact here is, that you can re-implement a driver in a more efficient way completely

Re: [riot-devel] Event driven drivers

2015-02-09 Thread Hauke Petersen
Hi again, On 09.02.2015 14:33, Kaspar Schleiser wrote: Hi Joakim, On 02/09/15 14:20, Joakim Gebart wrote: Has anyone measured the cost of the thread context switching on the different platforms? I'm mainly interested in Cortex-M4 (Kinetis). This would be a good indication of how slow an I/O

Re: [riot-devel] Event driven drivers

2015-02-08 Thread Ludwig Ortmann
Hi Frank, On Sun, Feb 08, 2015 at 11:47:25AM +0100, Frank Holtz wrote: i have looked into periph drivers and found a lot of single line while statements waiting for finishing things. ... Slow devices like ADC, Flash, UART or Random number generation are wasting a lot of CPU cycles while