Re: [PATCH v2] serial: exar: Fix stuck MSIs

[Andy Shevchenko]

On Mon, 2017-04-24 at 12:30 +0200, Jan Kiszka wrote:
> After migrating 8250_exar to MSI in 172c33cb61da, we can get stuck
> without further interrupts because of the special wake-up event these
> chips send. They are only cleared by reading INT0. As we fail to do so
> during startup and shutdown, we can leave the interrupt line asserted,
> which is fatal with edge-triggered MSIs.
> 
> Add the required reading of INT0 to startup and shutdown. Also account
> for the fact that a pending wake-up interrupt means we have to return
> 1
> from exar_handle_irq. Drop the unneeded reading of INT1..3 along with
> this - those never reset anything.
> 
> An alternative approach would have been disabling the wake-up
> interrupt.
> Unfortunately, this feature (REGB[17] = 1) is not available on the
> XR17D15X.

FWIW:
Reviewed-by: Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>

> 
> Fixes: 172c33cb61da ("serial: exar: Enable MSI support")
> Signed-off-by: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
> ---
> 
> Changes in v2:
> Â- mention removal of INT1..3 reading in commit log [Andy]
> ÂÂÂ(no functional changes)
> 
> Âdrivers/tty/serial/8250/8250_port.c | 19 ++++++++++---------
> Â1 file changed, 10 insertions(+), 9 deletions(-)
> 
> diff --git a/drivers/tty/serial/8250/8250_port.c
> b/drivers/tty/serial/8250/8250_port.c
> index 6119516ef5fc..3a3667880fcf 100644
> --- a/drivers/tty/serial/8250/8250_port.c
> +++ b/drivers/tty/serial/8250/8250_port.c
> @@ -47,6 +47,7 @@
> Â/*
> Â * These are definitions for the Exar XR17V35X and XR17(C|D)15X
> Â */
> +#define UART_EXAR_INT0		0x80
> Â#define UART_EXAR_SLEEP		0x8b	/* Sleep mode */
> Â#define UART_EXAR_DVID		0x8d	/* Device
> identification */
> Â
> @@ -1869,17 +1870,13 @@ static int
> serial8250_default_handle_irq(struct uart_port *port)
> Âstatic int exar_handle_irq(struct uart_port *port)
> Â{
> Â	unsigned int iir = serial_port_in(port, UART_IIR);
> -	int ret;
> +	int ret = 0;
> Â
> -	ret = serial8250_handle_irq(port, iir);
> +	if (((port->type == PORT_XR17V35X) || (port->type ==
> PORT_XR17D15X)) &&
> +	ÂÂÂÂserial_port_in(port, UART_EXAR_INT0) != 0)
> +		ret = 1;
> Â
> -	if ((port->type == PORT_XR17V35X) ||
> -	ÂÂÂ(port->type == PORT_XR17D15X)) {
> -		serial_port_in(port, 0x80);
> -		serial_port_in(port, 0x81);
> -		serial_port_in(port, 0x82);
> -		serial_port_in(port, 0x83);
> -	}
> +	ret |= serial8250_handle_irq(port, iir);
> Â
> Â	return ret;
> Â}
> @@ -2177,6 +2174,8 @@ int serial8250_do_startup(struct uart_port
> *port)
> Â	serial_port_in(port, UART_RX);
> Â	serial_port_in(port, UART_IIR);
> Â	serial_port_in(port, UART_MSR);
> +	if ((port->type == PORT_XR17V35X) || (port->type ==
> PORT_XR17D15X))
> +		serial_port_in(port, UART_EXAR_INT0);
> Â
> Â	/*
> Â	Â* At this point, there's no way the LSR could still be 0xff;
> @@ -2335,6 +2334,8 @@ int serial8250_do_startup(struct uart_port
> *port)
> Â	serial_port_in(port, UART_RX);
> Â	serial_port_in(port, UART_IIR);
> Â	serial_port_in(port, UART_MSR);
> +	if ((port->type == PORT_XR17V35X) || (port->type ==
> PORT_XR17D15X))
> +		serial_port_in(port, UART_EXAR_INT0);
> Â	up->lsr_saved_flags = 0;
> Â	up->msr_saved_flags = 0;
> Â

-- 
Andy Shevchenko <andriy.shevchenko@xxxxxxxxxxxxxxx>
Intel Finland Oy