From: Philippe Schenker <philippe.schenker@toradex.com>
To: "stefan@agner.ch" <stefan@agner.ch>
Cc: Max Krummenacher <max.krummenacher@toradex.com>,
"andrew.smirnov@gmail.com" <andrew.smirnov@gmail.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"fugang.duan@nxp.com" <fugang.duan@nxp.com>,
"linux-imx@nxp.com" <linux-imx@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"jslaby@suse.com" <jslaby@suse.com>
Subject: Re: [PATCH v1 2/3] tty: serial: lpuart: Use defines that correspond to correct register
Date: Thu, 17 Oct 2019 08:09:20 +0000 [thread overview]
Message-ID: <543cd256f408a175c734c7be5b5210839bc33b49.camel@toradex.com> (raw)
In-Reply-To: <8512c4712d0500c1c46186c2b52a7350@agner.ch>
On Wed, 2019-10-16 at 22:22 +0200, Stefan Agner wrote:
> On 2019-10-16 17:18, Philippe Schenker wrote:
> > Use UARTMODIR defines instead of UARTMODEM as it is a 32-bit
> > function
>
> This reads a bit strange at first. Also it is helpful for later to
> state
> that this does not make a difference in practise, so how about:
>
> Use define from the 32-bit register description UARTMODIR_* instead of
> UARTMODEM_*. The value is the same, so there is no functional change.
>
> Otherwise looks good to me:
>
> Reviewed-by: Stefan Agner <stefan.agner@toradex.com>
Thanks for your review and comment. And also thanks to Andy Duan for his
reviews!
You're right, I could have included that so it is clear that nothing is
changed. I will send a v2 today with your suggested commit message
Philippe
>
> --
> Stefan
>
> > Signed-off-by: Philippe Schenker <philippe.schenker@toradex.com>
> > ---
> >
> > drivers/tty/serial/fsl_lpuart.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/tty/serial/fsl_lpuart.c
> > b/drivers/tty/serial/fsl_lpuart.c
> > index f3271857621c..346b4a070ce9 100644
> > --- a/drivers/tty/serial/fsl_lpuart.c
> > +++ b/drivers/tty/serial/fsl_lpuart.c
> > @@ -1879,10 +1879,10 @@ lpuart32_set_termios(struct uart_port *port,
> > struct ktermios *termios,
> > }
> >
> > if (termios->c_cflag & CRTSCTS) {
> > - modem |= UARTMODEM_RXRTSE | UARTMODEM_TXCTSE;
> > + modem |= (UARTMODIR_RXRTSE | UARTMODIR_TXCTSE);
> > } else {
> > termios->c_cflag &= ~CRTSCTS;
> > - modem &= ~(UARTMODEM_RXRTSE | UARTMODEM_TXCTSE);
> > + modem &= ~(UARTMODIR_RXRTSE | UARTMODIR_TXCTSE);
> > }
> >
> > if (termios->c_cflag & CSTOPB)
next prev parent reply other threads:[~2019-10-17 8:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 15:18 [PATCH v1 1/3] tty: serial: lpuart: Remove unnecessary code from set_mctrl Philippe Schenker
2019-10-16 15:18 ` [PATCH v1 2/3] tty: serial: lpuart: Use defines that correspond to correct register Philippe Schenker
2019-10-16 20:22 ` Stefan Agner
2019-10-17 8:09 ` Philippe Schenker [this message]
2019-10-17 5:13 ` [EXT] " Andy Duan
2019-10-16 15:18 ` [PATCH v1 3/3] tty: serial: lpuart: Add RS485 support for 32-bit uart flavour Philippe Schenker
2019-10-17 5:14 ` [EXT] " Andy Duan
2019-10-17 5:13 ` [EXT] [PATCH v1 1/3] tty: serial: lpuart: Remove unnecessary code from set_mctrl Andy Duan
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=543cd256f408a175c734c7be5b5210839bc33b49.camel@toradex.com \
--to=philippe.schenker@toradex.com \
--cc=andrew.smirnov@gmail.com \
--cc=fugang.duan@nxp.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=max.krummenacher@toradex.com \
--cc=stefan@agner.ch \
/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
all inboxes | Powered by JetHome®