From: Lukas Wunner <lukas@wunner.de>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
John Ogness <john.ogness@linutronix.de>,
Lino Sanfilippo <LinoSanfilippo@gmx.de>,
linux-serial <linux-serial@vger.kernel.org>
Subject: Re: [PATCH tty-linus] serial: Reduce spinlocked portion of uart_rs485_config()
Date: Fri, 22 Sep 2023 06:04:33 +0200 [thread overview]
Message-ID: <20230922040433.GB9800@wunner.de> (raw)
In-Reply-To: <20230922040228.GA9800@wunner.de>
On Fri, Sep 22, 2023 at 06:02:28AM +0200, Lukas Wunner wrote:
> On Thu, Sep 21, 2023 at 06:01:41PM +0300, Ilpo Järvinen wrote:
> > On Thu, 21 Sep 2023, Lukas Wunner wrote:
> > > --- a/drivers/tty/serial/serial_core.c
> > > +++ b/drivers/tty/serial/serial_core.c
> > > @@ -1404,12 +1404,18 @@ static void uart_set_rs485_termination(struct uart_port *port,
> > > static int uart_rs485_config(struct uart_port *port)
> > > {
> > > struct serial_rs485 *rs485 = &port->rs485;
> > > + unsigned long flags;
> > > int ret;
> > >
> > > + if (!(rs485->flags & SER_RS485_ENABLED))
> > > + return 0;
> > > +
> > > uart_sanitize_serial_rs485(port, rs485);
> >
> > There's a subtle change in behavior here, uart_sanitize_serial_rs485()
> > memset()s rs485 if RS485 is not enabled but the early return above does
> > not.
>
> The two callers of uart_rs485_config() only call it if
> (!(uport->rs485.flags & SER_RS485_ENABLED)).
I meant to say "if (uport->rs485.flags & SER_RS485_ENABLED)"
(i.e. without negation).
Otherwise my point still stands. :)
> Adding that early return ensures that the behavior doesn't change.
>
> So I don't quite see why you think there's a change in behavior?
> Am I missing something?
next prev parent reply other threads:[~2023-09-22 4:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 14:52 [PATCH tty-linus] serial: Reduce spinlocked portion of uart_rs485_config() Lukas Wunner
2023-09-21 15:01 ` Ilpo Järvinen
2023-09-22 4:02 ` Lukas Wunner
2023-09-22 4:04 ` Lukas Wunner [this message]
2023-09-22 9:30 ` Ilpo Järvinen
2023-09-21 15:18 ` John Ogness
2023-09-21 15:23 ` Ilpo Järvinen
2023-09-22 4:23 ` Lukas Wunner
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=20230922040433.GB9800@wunner.de \
--to=lukas@wunner.de \
--cc=LinoSanfilippo@gmx.de \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=john.ogness@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.