From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Richard Genoud <richard.genoud@gmail.com>
Cc: Cyrille Pitchen <cyrille.pitchen@atmel.com>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCHv2 3/3] tty/serial: at91: fix hardware handshake on SAM9x5 (without GPIOs)
Date: Tue, 13 Sep 2016 15:45:56 +0200 [thread overview]
Message-ID: <20160913134556.wpodujgk6yn7rfxz@piout.net> (raw)
In-Reply-To: <CACQ1gAhNdPgtkpt1QPaiKjKi5oaq5vHbt4kKL5tQfwLvDBDo0w@mail.gmail.com>
On 12/09/2016 at 12:50:38 +0200, Richard Genoud wrote :
> >> diff --git a/drivers/tty/serial/atmel_serial.c b/drivers/tty/serial/atmel_serial.c
> >> index e9b4fbf88c2d..32154e7231ce 100644
> >> --- a/drivers/tty/serial/atmel_serial.c
> >> +++ b/drivers/tty/serial/atmel_serial.c
> >> @@ -2130,15 +2130,19 @@ static void atmel_set_termios(struct uart_port *port, struct ktermios *termios,
> >> } else if ((termios->c_cflag & CRTSCTS) &&
> >> !mctrl_gpio_use_rtscts(atmel_port->gpios)) {
> >> /*
> >> - * RS232 with hardware handshake (RTS/CTS)
> >> - * handled by the controller.
> >> + * Automatic hardware handshake (RTS/CTS) only work with
> >> + * FIFOs or PDC.
> >> + * Meaning that on SAM9x5 the controller can't handle
> >> + * the hardware handshake (no FIFOs nor PDC on these platforms).
> >> */
> >> - if (atmel_use_dma_rx(port) && !atmel_use_fifo(port)) {
> >> - dev_info(port->dev, "not enabling hardware flow control because DMA is used");
> >> - termios->c_cflag &= ~CRTSCTS;
> >> - } else {
> >> + if (atmel_use_pdc_rx(port) || atmel_use_fifo(port))
> >> mode |= ATMEL_US_USMODE_HWHS;
> >> - }
> >> + else
> >> + /*
> >> + * The hardware handshake won't be handle by the
> >> + * controller but by the driver.
> >> + */
> >> + mode |= ATMEL_US_USMODE_NORMAL;
> >
> > You still need the case where HWHS is impossible and there are no gpio
> > configured. You need to inform userspace that the configuration was not
> > applied instead of silently ignoring the error.
>
> Could you explain which case it is ?
> The only one I can see is when there's no GPIO declared for RTS/CTS
> AND, there's no pin muxed for RTS/CTS either.
>
> Have you got another example in mind ?
>
Hum, actually, it is that case. The other one (CRTSCTS and gpios) is
handled in the else below. I think you need to keep the termios->c_cflag
&= ~CRTSCTS; here so that userspace knows configuring it failed.
> >
> >> } else {
> >> /* RS232 without hadware handshake or controlled by GPIOs */
> >> mode |= ATMEL_US_USMODE_NORMAL;
> >
--
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-09-13 13:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-12 9:47 [PATCHv2 0/3] Fix handware handshake on SAM9x5 platforms Richard Genoud
2016-09-12 9:47 ` [PATCHv2 1/3] serial: mctrl_gpio: implement mctrl_gpio_use_rtscts Richard Genoud
2016-09-22 13:14 ` Uwe Kleine-König
2016-09-26 11:57 ` Richard Genoud
2016-09-12 9:47 ` [PATCHv2 2/3] tty/serial: at91: fix hardware handshake with GPIOs Richard Genoud
2016-09-22 9:47 ` Greg Kroah-Hartman
2016-09-22 13:20 ` Uwe Kleine-König
2016-09-27 7:45 ` Richard Genoud
2016-09-12 9:47 ` [PATCHv2 3/3] tty/serial: at91: fix hardware handshake on SAM9x5 (without GPIOs) Richard Genoud
2016-09-12 9:53 ` Alexandre Belloni
2016-09-12 10:50 ` Richard Genoud
2016-09-13 13:45 ` Alexandre Belloni [this message]
2016-09-14 10:31 ` Richard Genoud
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=20160913134556.wpodujgk6yn7rfxz@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=cyrille.pitchen@atmel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=richard.genoud@gmail.com \
/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®