Re: [PATCH v1] spi: check tx_buf and rx_buf in spi_unmap_msg

2015-04-16 Thread Mark Brown
On Thu, Apr 16, 2015 at 10:54:18AM +0800, Robin Gong wrote: > Some spi device drivers use the same tx_buf and rx_buf repeatly for better > performance such as driver/input/touchsreen/ads7846.c, but spi core grab > tx_buf > /rx_buf of transfer and set them as dummy_tx/dummy_rx once they are NULL.

Re: [PATCH v1] spi: check tx_buf and rx_buf in spi_unmap_msg

2015-04-16 Thread Mark Brown
On Thu, Apr 16, 2015 at 10:54:18AM +0800, Robin Gong wrote: Some spi device drivers use the same tx_buf and rx_buf repeatly for better performance such as driver/input/touchsreen/ads7846.c, but spi core grab tx_buf /rx_buf of transfer and set them as dummy_tx/dummy_rx once they are NULL.

[PATCH v1] spi: check tx_buf and rx_buf in spi_unmap_msg

2015-04-15 Thread Robin Gong
Some spi device drivers use the same tx_buf and rx_buf repeatly for better performance such as driver/input/touchsreen/ads7846.c, but spi core grab tx_buf /rx_buf of transfer and set them as dummy_tx/dummy_rx once they are NULL. Thus, in the second time the tx_buf/rx_buf will be replaced by

[PATCH v1] spi: check tx_buf and rx_buf in spi_unmap_msg

2015-04-15 Thread Robin Gong
Some spi device drivers use the same tx_buf and rx_buf repeatly for better performance such as driver/input/touchsreen/ads7846.c, but spi core grab tx_buf /rx_buf of transfer and set them as dummy_tx/dummy_rx once they are NULL. Thus, in the second time the tx_buf/rx_buf will be replaced by