Re: [PATCH V2 2/2] spi/bcm63xx: work around inability to keep CS up

2013-02-05 Thread Grant Likely
On Sun, 3 Feb 2013 15:15:13 +0100, Jonas Gorski j...@openwrt.org wrote: This SPI controller does not support keeping CS asserted after sending a transfer. Since messages expected on this SPI controller are rather short, we can work around it for normal use cases by sending all transfers at

Re: [PATCH V2 2/2] spi/bcm63xx: work around inability to keep CS up

2013-02-05 Thread Jonas Gorski
On Tue, 05 Feb 2013 14:35:30 + Grant Likely grant.lik...@secretlab.ca wrote: On Sun, 3 Feb 2013 15:15:13 +0100, Jonas Gorski j...@openwrt.org wrote: This SPI controller does not support keeping CS asserted after sending a transfer. Since messages expected on this SPI controller are

Re: [PATCH V2 2/2] spi/bcm63xx: work around inability to keep CS up

2013-02-05 Thread Grant Likely
On Tue, 5 Feb 2013 16:00:04 +0100, Jonas Gorski j...@openwrt.org wrote: On Tue, 05 Feb 2013 14:35:30 + Grant Likely grant.lik...@secretlab.ca wrote: On Sun, 3 Feb 2013 15:15:13 +0100, Jonas Gorski j...@openwrt.org wrote: This SPI controller does not support keeping CS asserted after

[PATCH V2 2/2] spi/bcm63xx: work around inability to keep CS up

2013-02-03 Thread Jonas Gorski
This SPI controller does not support keeping CS asserted after sending a transfer. Since messages expected on this SPI controller are rather short, we can work around it for normal use cases by sending all transfers at once in a big full duplex stream. This means that we cannot change the speed