From: Mark Rutland <mark.rutland@arm.com>
To: Murali Karicheri <m-karicheri2@ti.com>
Cc: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>,
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 v1] serial: uart: add hw flow control support configuration
Date: Tue, 29 Apr 2014 15:27:57 -0700 [thread overview]
Message-ID: <20140429222756.GA2382@flaeskesteg> (raw)
In-Reply-To: <1398792122-18592-1-git-send-email-m-karicheri2@ti.com>
Hi,
On Tue, Apr 29, 2014 at 06:22:02PM +0100, 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>
> ---
> - Fixed brackets around port->flags & UPF_HARD_FLOW as per comments
> .../devicetree/bindings/serial/of-serial.txt | 2 ++
> 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, 19 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/serial/of-serial.txt b/Documentation/devicetree/bindings/serial/of-serial.txt
> index 1928a3e..123de01 100644
> --- a/Documentation/devicetree/bindings/serial/of-serial.txt
> +++ b/Documentation/devicetree/bindings/serial/of-serial.txt
> @@ -37,6 +37,8 @@ Optional properties:
> - auto-flow-control: one way to enable automatic flow control support. The
> driver is allowed to detect support for the capability even without this
> property.
> +- hw-flow-control: this enables pure hw flow control and no software
> + intervention needed.
>From the wording of the commit message, I believe this would be better worded
something like:
- hw-flow-control: the hardware has flow control capability.
While the OS needs to know that flow control is present if it wishes to make
use of it, whether or not the OS does so is not a matter for the binding.
It might also be better worded as "has-hw-flow-control", which would make that
distinction clearer.
Otherwise this looks fine to me.
Thanks,
Mark.
next prev parent reply other threads:[~2014-04-29 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 17:22 [PATCH v1] serial: uart: add hw flow control support configuration Murali Karicheri
2014-04-29 22:27 ` Mark Rutland [this message]
2014-05-01 18:57 ` Karicheri, Muralidharan
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=20140429222756.GA2382@flaeskesteg \
--to=mark.rutland@arm.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).