summaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/reset/zynq-reset.txt
diff options
context:
space:
mode:
authorTan, Jui Nee2015-09-01 04:22:51 +0200
committerMark Brown2015-09-02 11:17:45 +0200
commit02bc933ebb59208f42c2e6305b2c17fd306f695d (patch)
tree85433507405b02c4244ccb51d59e9839fc8cd7a2 /Documentation/devicetree/bindings/reset/zynq-reset.txt
parentLinux 4.2-rc1 (diff)
downloadkernel-qcow2-linux-02bc933ebb59208f42c2e6305b2c17fd306f695d.tar.gz
kernel-qcow2-linux-02bc933ebb59208f42c2e6305b2c17fd306f695d.tar.xz
kernel-qcow2-linux-02bc933ebb59208f42c2e6305b2c17fd306f695d.zip
spi: spi-pxa2xx: Check status register to determine if SSSR_TINT is disabled
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> Cc: stable@vger.kernel.org
Diffstat (limited to 'Documentation/devicetree/bindings/reset/zynq-reset.txt')
0 files changed, 0 insertions, 0 deletions