From: Scott E. <sc...@ju...> - 2014-09-05 09:53:39
|
Here are some instructions (using this spi rt change as an example) http://www.jumpnowtek.com/overo/overo-kernel-development-simple-patching.html >From the booted system overo login: root root@overo:~# dmesg | grep spi [ 1.469177] spi_master spi1: will run message pump with realtime priority [ 1.481201] spi_master spi2: will run message pump with realtime priority [ 1.488769] spi_master spi3: will run message pump with realtime priority [ 1.496368] spi_master spi4: will run message pump with realtime priority [ 4.531738] ads7846 spi1.0: touchscreen, irq 210 [ 4.558105] ads7846 spi1.0: no device detected, test read result was 0x00000FFF I am not saying this is going to help with your original issue. I made this change once for a Duovero SPI project, but I don't have the numbers around for the change in performance. I remember there was an impact on the USB subsystem though. It was a tradeoff. This change might make the system worse with the single-core Overo. It's just an idea and (I thought ;-) easy enough to try. -- View this message in context: http://gumstix.8.x6.nabble.com/SPI-and-multi-threading-issue-tp4969428p4969448.html Sent from the Gumstix mailing list archive at Nabble.com. |