Re: [PATCH 11/18] spi: qup: properly detect extra interrupts

2017-06-14 Thread Sricharan R
Hi Andy, On 6/15/2017 1:29 AM, Andy Gross wrote: > On Wed, Jun 14, 2017 at 12:57:25PM +0530, Sricharan R wrote: >> Hi Varada, >> >> On 6/14/2017 11:22 AM, Varadarajan Narayanan wrote: >>> It's possible for a SPI transaction to complete and get another >>> interrupt and have it processed on the sam

Re: [PATCH 11/18] spi: qup: properly detect extra interrupts

2017-06-14 Thread Matthew McClintock
On Wed, Jun 14, 2017 at 2:59 PM, Andy Gross wrote: > On Wed, Jun 14, 2017 at 12:57:25PM +0530, Sricharan R wrote: >> Hi Varada, >> >> On 6/14/2017 11:22 AM, Varadarajan Narayanan wrote: >> > It's possible for a SPI transaction to complete and get another >> > interrupt and have it processed on the

Re: [PATCH 11/18] spi: qup: properly detect extra interrupts

2017-06-14 Thread Andy Gross
On Wed, Jun 14, 2017 at 12:57:25PM +0530, Sricharan R wrote: > Hi Varada, > > On 6/14/2017 11:22 AM, Varadarajan Narayanan wrote: > > It's possible for a SPI transaction to complete and get another > > interrupt and have it processed on the same spi_transfer before the > > transfer_one can set it

Re: [PATCH 11/18] spi: qup: properly detect extra interrupts

2017-06-14 Thread Sricharan R
Hi Varada, On 6/14/2017 11:22 AM, Varadarajan Narayanan wrote: > It's possible for a SPI transaction to complete and get another > interrupt and have it processed on the same spi_transfer before the > transfer_one can set it to NULL. > > This masks unexpected interrupts, so let's set the spi_tran

[PATCH 11/18] spi: qup: properly detect extra interrupts

2017-06-13 Thread Varadarajan Narayanan
It's possible for a SPI transaction to complete and get another interrupt and have it processed on the same spi_transfer before the transfer_one can set it to NULL. This masks unexpected interrupts, so let's set the spi_transfer to NULL in the interrupt once the transaction is done. So we can prop