public inbox for linux-serial@vger.kernel.org
 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>,
	 Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH v2 1/5] serial: 8250: extract serial8250_init_mctrl()
Date: Tue, 24 Jun 2025 14:15:27 +0300 (EEST)	[thread overview]
Message-ID: <4d6b65af-294c-fd02-af91-099e22420472@linux.intel.com> (raw)
In-Reply-To: <b78023eb-f5ab-6287-1cd7-5db76d905eed@linux.intel.com>

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

On Tue, 24 Jun 2025, Ilpo Järvinen wrote:

> On Tue, 24 Jun 2025, Jiri Slaby (SUSE) wrote:
> 
> > After commit 795158691cc0 ("serial: 8250: extract
> > serial8250_initialize()"), split serial8250_initialize() even more --
> > the mctrl part of this code can be separated into
> > serial8250_init_mctrl() -- done now.
> > 
> > Signed-off-by: Jiri Slaby (SUSE) <jirislaby@kernel.org>
> > Suggested-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> 
> Heh, I didn't even realize I was suggesting this :-D but it's good 
> nonetheless.
> 
> Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> 
> > Cc: Andy Shevchenko <andy.shevchenko@gmail.com>
> > ---
> > [v2]
> > * use port-> directly.
> > * do not remove curly braces.
> > Both rebase errors -- noticed by Andy.
> > ---
> >  drivers/tty/serial/8250/8250_port.c | 21 +++++++++++++--------
> >  1 file changed, 13 insertions(+), 8 deletions(-)
> > 
> > diff --git a/drivers/tty/serial/8250/8250_port.c b/drivers/tty/serial/8250/8250_port.c
> > index 48c30e158cb8..0f85a2f292fc 100644
> > --- a/drivers/tty/serial/8250/8250_port.c
> > +++ b/drivers/tty/serial/8250/8250_port.c
> > @@ -2216,15 +2216,8 @@ static void serial8250_THRE_test(struct uart_port *port)
> >  		up->bugs |= UART_BUG_THRE;
> >  }
> >  
> > -static void serial8250_initialize(struct uart_port *port)
> > +static void serial8250_init_mctrl(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);
> > -
> > -	uart_port_lock_irqsave(port, &flags);
> >  	if (port->flags & UPF_FOURPORT) {

I should have also added what I meant with my earlier suggestion. AFAICT, 
this UPF_FOURPORT thing can only occur if SERIAL_8250_FOURPORT is enabled.

The challenge obviously are the if/else constructs but there are a few 
places that do port->flags & UPF_FOURPORT specific thing and something 
else otherwise. That hw-specific code could be placed into the hw-specific 
8250_fourport.c file if the hw-specific function is made to return true 
if it did match, and the generic code runs otherwise.

I also have no idea why serial/sunsu.c checks UPF_FOURPORT, perhaps that's 
copy-paste in action. :-)

> >  		if (!port->irq)
> >  			port->mctrl |= TIOCM_OUT1;
> > @@ -2235,6 +2228,18 @@ static void serial8250_initialize(struct uart_port *port)
> >  	}
> >  
> >  	serial8250_set_mctrl(port, port->mctrl);
> > +}
> > +
> > +static void serial8250_initialize(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);
> > +
> > +	uart_port_lock_irqsave(port, &flags);
> > +	serial8250_init_mctrl(port);
> >  
> >  	/*
> >  	 * Serial over Lan (SoL) hack:
> > 
> 
> 

-- 
 i.

  reply	other threads:[~2025-06-24 11:15 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 [this message]
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
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=4d6b65af-294c-fd02-af91-099e22420472@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=andy.shevchenko@gmail.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