linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Jiri Slaby (SUSE)" <jirislaby@kernel.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	 linux-serial <linux-serial@vger.kernel.org>,
	 LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/5] serial: 8250: extract serial8250_iir_txen_test()
Date: Tue, 24 Jun 2025 14:05:18 +0300 (EEST)	[thread overview]
Message-ID: <a77e5a15-0eb8-02ed-c279-80cba3e51ff1@linux.intel.com> (raw)
In-Reply-To: <20250624080641.509959-3-jirislaby@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 3655 bytes --]

On Tue, 24 Jun 2025, Jiri Slaby (SUSE) wrote:

> After commit 795158691cc0 ("serial: 8250: extract
> serial8250_initialize()"), split serial8250_initialize() even more --
> the TX enable test part of this code can be separated into
> serial8250_iir_txen_test().
> 
> Signed-off-by: Jiri Slaby (SUSE) <jirislaby@kernel.org>
> Suggested-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> ---
>  drivers/tty/serial/8250/8250_port.c | 49 ++++++++++++++++-------------
>  1 file changed, 28 insertions(+), 21 deletions(-)
> 
> diff --git a/drivers/tty/serial/8250/8250_port.c b/drivers/tty/serial/8250/8250_port.c
> index 0f85a2f292fc..5bb0ca04da55 100644
> --- a/drivers/tty/serial/8250/8250_port.c
> +++ b/drivers/tty/serial/8250/8250_port.c
> @@ -2230,16 +2230,19 @@ static void serial8250_init_mctrl(struct uart_port *port)
>  	serial8250_set_mctrl(port, port->mctrl);
>  }
>  
> -static void serial8250_initialize(struct uart_port *port)
> +static void serial8250_iir_txen_test(struct uart_port *port)
>  {
>  	struct uart_8250_port *up = up_to_u8250p(port);
> -	unsigned long flags;
>  	bool lsr_TEMT, iir_NOINT;
>  
> -	serial_port_out(port, UART_LCR, UART_LCR_WLEN8);
> +	if (port->quirks & UPQ_NO_TXEN_TEST)
> +		return;
>  
> -	uart_port_lock_irqsave(port, &flags);
> -	serial8250_init_mctrl(port);
> +	/* Do a quick test to see if we receive an interrupt when we enable the TX irq. */
> +	serial_port_out(port, UART_IER, UART_IER_THRI);
> +	lsr_TEMT = serial_port_in(port, UART_LSR) & UART_LSR_TEMT;
> +	iir_NOINT = serial_port_in(port, UART_IIR) & UART_IIR_NO_INT;
> +	serial_port_out(port, UART_IER, 0);
>  
>  	/*
>  	 * Serial over Lan (SoL) hack:
> @@ -2247,26 +2250,30 @@ static void serial8250_initialize(struct uart_port *port)
>  	 * Lan.  Those chips take a longer time than a normal serial device to signalize that a
>  	 * transmission data was queued. Due to that, the above test generally fails. One solution
>  	 * would be to delay the reading of iir. However, this is not reliable, since the timeout is
> -	 * variable. So, let's just don't test if we receive TX irq.  This way, we'll never enable
> -	 * UART_BUG_TXEN.
> +	 * variable. So, in case of UPQ_NO_TXEN_TEST, let's just don't test if we receive TX irq.
> +	 * This way, we'll never enable UART_BUG_TXEN.
>  	 */
> -	if (!(port->quirks & UPQ_NO_TXEN_TEST)) {
> -		/* Do a quick test to see if we receive an interrupt when we enable the TX irq. */
> -		serial_port_out(port, UART_IER, UART_IER_THRI);
> -		lsr_TEMT = serial_port_in(port, UART_LSR) & UART_LSR_TEMT;
> -		iir_NOINT = serial_port_in(port, UART_IIR) & UART_IIR_NO_INT;
> -		serial_port_out(port, UART_IER, 0);
> -
> -		if (lsr_TEMT && iir_NOINT) {
> -			if (!(up->bugs & UART_BUG_TXEN)) {
> -				up->bugs |= UART_BUG_TXEN;
> -				dev_dbg(port->dev, "enabling bad tx status workarounds\n");
> -			}
> -		} else {
> -			up->bugs &= ~UART_BUG_TXEN;
> +	if (lsr_TEMT && iir_NOINT) {
> +		if (!(up->bugs & UART_BUG_TXEN)) {
> +			up->bugs |= UART_BUG_TXEN;
> +			dev_dbg(port->dev, "enabling bad tx status workarounds\n");
>  		}
> +		return;
>  	}
>  
> +	/* FIXME: why is this needed? */
> +	up->bugs &= ~UART_BUG_TXEN;
> +}
> +
> +static void serial8250_initialize(struct uart_port *port)
> +{
> +	unsigned long flags;
> +
> +	serial_port_out(port, UART_LCR, UART_LCR_WLEN8);
> +
> +	uart_port_lock_irqsave(port, &flags);
> +	serial8250_init_mctrl(port);
> +	serial8250_iir_txen_test(port);
>  	uart_port_unlock_irqrestore(port, flags);
>  }
>  
> 

Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>

-- 
 i.

  reply	other threads:[~2025-06-24 11:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24  8:06 [PATCH v2 0/5] tty: fixes on top of summer cleanup Jiri Slaby (SUSE)
2025-06-24  8:06 ` [PATCH v2 1/5] serial: 8250: extract serial8250_init_mctrl() Jiri Slaby (SUSE)
2025-06-24 11:02   ` Ilpo Järvinen
2025-06-24 11:15     ` Ilpo Järvinen
2025-06-25  5:59       ` Jiri Slaby
2025-06-24 14:10   ` Andy Shevchenko
2025-06-24  8:06 ` [PATCH v2 2/5] serial: 8250: extract serial8250_iir_txen_test() Jiri Slaby (SUSE)
2025-06-24 11:05   ` Ilpo Järvinen [this message]
2025-06-24 14:11   ` Andy Shevchenko
2025-06-24  8:06 ` [PATCH v2 3/5] serial: 8250: rename lsr_TEMT, iir_NOINT to lowercase Jiri Slaby (SUSE)
2025-06-24 11:15   ` Ilpo Järvinen
2025-06-24 14:12   ` Andy Shevchenko
2025-06-24  8:06 ` [PATCH v2 4/5] serial: 8250: document doubled "type == PORT_8250_CIR" check Jiri Slaby (SUSE)
2025-06-24 11:16   ` Ilpo Järvinen
2025-06-24  8:06 ` [PATCH v2 5/5] tty: fix tty_port_tty_*hangup() kernel-doc Jiri Slaby (SUSE)
2025-06-24 11:00   ` Ilpo Järvinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=a77e5a15-0eb8-02ed-c279-80cba3e51ff1@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).