On 10/06/2016 04:37 AM, Mark Brown wrote:
On Wed, Oct 05, 2016 at 04:38:58PM -0500, ttha...@opensource.altera.com wrote:
This patch adds the Slave Select locally so that the transfer will
start and complete. The GPIO CS is taken care of earlier in the SPI
framework (spi_set_cs).
This seems
On 10/06/2016 04:37 AM, Mark Brown wrote:
On Wed, Oct 05, 2016 at 04:38:58PM -0500, ttha...@opensource.altera.com wrote:
This patch adds the Slave Select locally so that the transfer will
start and complete. The GPIO CS is taken care of earlier in the SPI
framework (spi_set_cs).
This seems
On Wed, Oct 05, 2016 at 04:38:58PM -0500, ttha...@opensource.altera.com wrote:
> This patch adds the Slave Select locally so that the transfer will
> start and complete. The GPIO CS is taken care of earlier in the SPI
> framework (spi_set_cs).
This seems like something that other devices might
On Wed, Oct 05, 2016 at 04:38:58PM -0500, ttha...@opensource.altera.com wrote:
> This patch adds the Slave Select locally so that the transfer will
> start and complete. The GPIO CS is taken care of earlier in the SPI
> framework (spi_set_cs).
This seems like something that other devices might
From: Thor Thayer
Currently in the GPIO CS case, the transfer is stalled. The DesignWare
IP datasheet points out that the slave must be selected (SER) before the
transfer can start [1]. The SPI framework selects the chip using either
1) the internal CS mechanism or
From: Thor Thayer
Currently in the GPIO CS case, the transfer is stalled. The DesignWare
IP datasheet points out that the slave must be selected (SER) before the
transfer can start [1]. The SPI framework selects the chip using either
1) the internal CS mechanism or 2) the GPIO CS, but not both.
6 matches
Mail list logo