aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/staging/fbtft/fbtft-io.c
diff options
context:
space:
mode:
authorAndy Shevchenko <andriy.shevchenko@linux.intel.com>2017-01-19 12:45:42 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2017-01-19 12:50:27 +0100
commit7c3eaadd0209fe21f331600ea2d904c3a0e9b287 (patch)
tree4d3ef83783af3ed0a263a61808e04dcd713ab63e /drivers/staging/fbtft/fbtft-io.c
parentstaging: fbtft: convert fbtft_reset() to be non-atomic (diff)
downloadlinux-dev-7c3eaadd0209fe21f331600ea2d904c3a0e9b287.tar.xz
linux-dev-7c3eaadd0209fe21f331600ea2d904c3a0e9b287.zip
staging: fbtft: remove custom DMA mapped buffer
There is no need to duplicate what SPI core already does, i.e. mapping buffers for DMA capable transfers. Remove all related pices of code. Note, that code, besides its redundancy, was buggy: DMA address potentially can be 0, SPI slave device has nothing to do with DMA capable device properties and DMA mask in particular. Suggested-by: Noralf Trønnes <noralf@tronnes.org> Acked-by: Noralf Trønnes <noralf@tronnes.org> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/staging/fbtft/fbtft-io.c')
-rw-r--r--drivers/staging/fbtft/fbtft-io.c4
1 files changed, 0 insertions, 4 deletions
diff --git a/drivers/staging/fbtft/fbtft-io.c b/drivers/staging/fbtft/fbtft-io.c
index 4dcea2e0b3ae..d86840548b74 100644
--- a/drivers/staging/fbtft/fbtft-io.c
+++ b/drivers/staging/fbtft/fbtft-io.c
@@ -22,10 +22,6 @@ int fbtft_write_spi(struct fbtft_par *par, void *buf, size_t len)
}
spi_message_init(&m);
- if (par->txbuf.dma && buf == par->txbuf.buf) {
- t.tx_dma = par->txbuf.dma;
- m.is_dma_mapped = 1;
- }
spi_message_add_tail(&t, &m);
return spi_sync(par->spi, &m);
}