linux-kernel - Re: [PATCH] spi: spi-pxa2xx: Check status register to determine if SSSR

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <55E556BE.1020705@linux.intel.com>
Date:	Tue, 01 Sep 2015 10:41:50 +0300
From:	Jarkko Nikula <jarkko.nikula@...ux.intel.com>
To:	Tan Jui Nee <jui.nee.tan@...el.com>, broonie@...nel.org
CC:	linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
	mika.westerberg@...ux.intel.com
Subject: Re: [PATCH] spi: spi-pxa2xx: Check status register to determine if
 SSSR_TINT is disabled

On 09/01/2015 05:22 AM, Tan Jui Nee wrote:
> From: "Tan, Jui Nee" <jui.nee.tan@...el.com>
>
> 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@...el.com>
> ---
>   drivers/spi/spi-pxa2xx.c | 4 ++++
>   1 file changed, 4 insertions(+)
>
Acked-by: Jarkko Nikula <jarkko.nikula@...ux.intel.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/