From: Peter Hurley <peter@hurleysoftware.com>
To: Murali Karicheri <m-karicheri2@ti.com>,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Randy Dunlap <rdunlap@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>,
Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: Re: [PATCH v2] serial: uart: add hw flow control support configuration
Date: Thu, 07 Aug 2014 11:29:08 -0400 [thread overview]
Message-ID: <53E39B44.60406@hurleysoftware.com> (raw)
In-Reply-To: <1398971093-17164-1-git-send-email-m-karicheri2@ti.com>
On 05/01/2014 03:04 PM, Murali Karicheri wrote:
> 8250 uart driver currently supports only software assisted hw flow
> control. The software assisted hw flow control maintains a hw_stopped
> flag in the tty structure to stop and start transmission and use modem
> status interrupt for the event to drive the handshake signals. This is
> not needed if hw has flow control capabilities. This patch adds a
> DT attribute for enabling hw flow control for a uart port. Also skip
> stop and start if this flag is present in flag field of the port
> structure.
>
> Signed-off-by: Murali Karicheri <m-karicheri2@ti.com>
>
> CC: Rob Herring <robh+dt@kernel.org>
> CC: Pawel Moll <pawel.moll@arm.com>
> CC: Mark Rutland <mark.rutland@arm.com>
> CC: Ian Campbell <ijc+devicetree@hellion.org.uk>
> CC: Kumar Gala <galak@codeaurora.org>
> CC: Randy Dunlap <rdunlap@infradead.org>
> CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> CC: Jiri Slaby <jslaby@suse.cz>
> CC: Santosh Shilimkar <santosh.shilimkar@ti.com>
> ---
> .../devicetree/bindings/serial/of-serial.txt | 1 +
> drivers/tty/serial/8250/8250_core.c | 6 ++++--
> drivers/tty/serial/of_serial.c | 4 ++++
> drivers/tty/serial/serial_core.c | 12 +++++++++---
> 4 files changed, 18 insertions(+), 5 deletions(-)
>
[...]
> diff --git a/drivers/tty/serial/serial_core.c b/drivers/tty/serial/serial_core.c
> index b68550d..851707a 100644
> --- a/drivers/tty/serial/serial_core.c
> +++ b/drivers/tty/serial/serial_core.c
> @@ -174,8 +174,12 @@ static int uart_port_startup(struct tty_struct *tty, struct uart_state *state,
> if (tty->termios.c_cflag & CBAUD)
> uart_set_mctrl(uport, TIOCM_RTS | TIOCM_DTR);
> }
> -
> - if (tty_port_cts_enabled(port)) {
> + /*
> + * if hw support flow control without software intervention,
> + * then skip the below check
> + */
> + if (tty_port_cts_enabled(port) &&
> + !(uport->flags & UPF_HARD_FLOW)) {
> spin_lock_irq(&uport->lock);
> if (!(uport->ops->get_mctrl(uport) & TIOCM_CTS))
> tty->hw_stopped = 1;
> @@ -2772,7 +2776,9 @@ void uart_handle_cts_change(struct uart_port *uport, unsigned int status)
>
> uport->icount.cts++;
>
> - if (tty_port_cts_enabled(port)) {
> + /* skip below code if the hw flow control is supported */
> + if (tty_port_cts_enabled(port) &&
> + !(uport->flags & UPF_HARD_FLOW)) {
Why is a modem status interrupt being generated for DCTS
if autoflow control is enabled?
This should be:
WARN_ON_ONCE(uport->flags & UPF_HARD_FLOW);
to indicate a mis-configured driver/device.
> if (tty->hw_stopped) {
> if (status) {
> tty->hw_stopped = 0;
>
next prev parent reply other threads:[~2014-08-07 15:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 19:04 [PATCH v2] serial: uart: add hw flow control support configuration Murali Karicheri
2014-05-01 19:04 ` Murali Karicheri
2014-05-09 15:30 ` Karicheri, Muralidharan
2014-05-28 20:04 ` Dann Frazier
2014-06-11 20:53 ` Murali Karicheri
[not found] ` <5398C1D0.30808-l0cyMroinI0@public.gmane.org>
2014-06-11 21:05 ` Dann Frazier
2014-06-11 21:05 ` Dann Frazier
2014-08-07 15:29 ` Peter Hurley [this message]
2014-08-07 16:16 ` Murali Karicheri
2014-08-07 16:16 ` Murali Karicheri
2014-08-07 17:12 ` Greg Kroah-Hartman
2014-08-07 17:24 ` Murali Karicheri
2014-08-07 17:24 ` Murali Karicheri
2014-08-07 17:25 ` Peter Hurley
2014-08-07 17:34 ` Murali Karicheri
2014-08-07 17:34 ` Murali Karicheri
2014-08-07 18:33 ` Peter Hurley
2014-08-07 20:46 ` Murali Karicheri
2014-08-07 20:46 ` Murali Karicheri
2014-08-07 23:03 ` Peter Hurley
2014-08-08 19:36 ` Murali Karicheri
2014-08-08 19:36 ` Murali Karicheri
2014-08-08 20:44 ` Peter Hurley
2014-08-08 21:02 ` Murali Karicheri
2014-08-08 21:02 ` Murali Karicheri
2014-08-08 22:09 ` Peter Hurley
2014-08-08 22:59 ` Murali Karicheri
2014-08-08 22:59 ` Murali Karicheri
2014-08-09 11:28 ` Murali Karicheri
2014-08-09 11:28 ` Murali Karicheri
2014-08-19 15:29 ` Murali Karicheri
2014-08-19 15:29 ` Murali Karicheri
2014-08-21 19:33 ` Peter Hurley
2014-08-22 16:45 ` Murali Karicheri
2014-08-22 16:45 ` Murali Karicheri
2014-08-08 20:46 ` Murali Karicheri
2014-08-08 20:46 ` Murali Karicheri
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=53E39B44.60406@hurleysoftware.com \
--to=peter@hurleysoftware.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jslaby@suse.cz \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=santosh.shilimkar@ti.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 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.