On MX23 the XFER_COUNT part in ctrl0 field in DMA descriptor was improperly
OR'd during the construction of DMA descriptor chain, instead of being
freshly set.
Because of that too many bytes were being expected from SPI during the last
DMA cycle.
This caused a timeout (SSP_TIMEOUT) to happen in the
Dear Juha Lumme,
> On MX23 the XFER_LEN
XFER_COUNT ;-)
> part in CTRL0 register was improperly OR'd
... during construction of DMA descriptor chain. Instead of being freshly set.
> , and
> because of that too many characters
Bytes
> were being expected from SPI.
expected from SPI during the
On MX23 the XFER_LEN part in CTRL0 register was improperly OR'd, and because
of that too many characters were being expected from SPI.
This caused a timeout (SSP_TIMEOUT) to happen in the last package in the DMA
chain, and resulted into a corrupted read.
This is a workaround for the problem, by cle
From: Barry Song
Convert clk_enable/clk_disable to clk_prepare_enable/clk_disable_unprepare
calls as required by common clock framework.
Signed-off-by: Barry Song
---
drivers/spi/spi-sirf.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/spi/spi-sirf.c b/d
From: Barry Song
the driver is also compatible with SiRFmarco except SiRFprimaII,
so simply add "sirf,marco-spi" to OF match table.
Signed-off-by: Barry Song
---
drivers/spi/spi-sirf.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/spi/spi-sirf.c b/drivers/spi