summaryrefslogtreecommitdiff
path: root/mm
diff options
context:
space:
mode:
authorTan, Jui Nee <jui.nee.tan@intel.com>2015-09-01 10:22:51 +0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2015-10-22 14:37:50 -0700
commit69155df6a85cd1672c032220a8619a7f9e5f403b (patch)
tree95aeb66d2eb0be19fa9430fa7c525006fe2d97ce /mm
parent69e686057711bf17907ba68e19ceffdfca80d788 (diff)
downloadlwn-69155df6a85cd1672c032220a8619a7f9e5f403b.tar.gz
lwn-69155df6a85cd1672c032220a8619a7f9e5f403b.zip
spi: spi-pxa2xx: Check status register to determine if SSSR_TINT is disabled
commit 02bc933ebb59208f42c2e6305b2c17fd306f695d upstream. On Intel Baytrail, there is case when interrupt handler get called, no SPI message is captured. The RX FIFO is indeed empty when RX timeout pending interrupt (SSSR_TINT) happens. Use the BIOS version where both HSUART and SPI are on the same IRQ. Both drivers are using IRQF_SHARED when calling the request_irq function. When running two separate and independent SPI and HSUART application that generate data traffic on both components, user will see messages like below on the console: pxa2xx-spi pxa2xx-spi.0: bad message state in interrupt handler This commit will fix this by first checking Receiver Time-out Interrupt, if it is disabled, ignore the request and return without servicing. Signed-off-by: Tan, Jui Nee <jui.nee.tan@intel.com> Acked-by: Jarkko Nikula <jarkko.nikula@linux.intel.com> Signed-off-by: Mark Brown <broonie@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'mm')
0 files changed, 0 insertions, 0 deletions