summaryrefslogtreecommitdiffstats
path: root/fs
diff options
context:
space:
mode:
authorJean-Christophe Lallemand <jcl@develtech.com>2008-11-12 13:27:00 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2008-11-12 17:17:17 -0800
commit50d7d5bf3168db5d04566dd7ffb9a820e9fdf484 (patch)
tree55eba6757e8068e2a85d886d99701118f73f9170 /fs
parent79b92f2bab0dc5ac70e8391548f75ac3268426e4 (diff)
downloadop-kernel-dev-50d7d5bf3168db5d04566dd7ffb9a820e9fdf484.zip
op-kernel-dev-50d7d5bf3168db5d04566dd7ffb9a820e9fdf484.tar.gz
atmel_spi: work-around required for new HW bug in AT91SAM9263 Rev.B SPI controller
We're working with an AT91SAM9263 Rev B in our design and I experienced some inconsistency in spi-based touchscreen usage between our board and the Atmel evaluation kit we have that runs on a Rev A chip. The data was apparently delayed by 1 byte and got ridiculous data out of the touchscreen driver, very strange. As everything looked normal in the spi, touchscreen and dma logs, I contacted the Atmel support and they triggered me on a new HW bug that appeared in the Rev B SPI controller. The problem is that the SPI controller on the Rev B needs that the software reset is performed two times so that it's performed correctly. Applying the patch below solves the issue on my Rev B board. I've tested it as well on my Rev A evaluation kit and it has apparently no unwanted side effect, things continue to work as expected. Signed-off-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com> Cc: David Brownell <david-b@pacbell.net> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud