From: Jason Uy <jason.uy@broadcom.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Kefeng Wang <wangkefeng.wang@huawei.com>,
Noam Camus <noamc@ezchip.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Wang Hongcheng <annie.wang@amd.com>,
Jason Uy <jason.uy@broadcom.com>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: [PATCH v1 0/1] serial: 8250_dw: Allow hardware flow control to be used
Date: Tue, 6 Dec 2016 14:34:02 -0800 [thread overview]
Message-ID: <1481063643-11951-1-git-send-email-jason.uy@broadcom.com> (raw)
This patchset contains changes to allow AUTOCTS to be set for the Synopsys DW UART driver. There is currently no way to set AUTOCTS unless the platform adds a quirk entry and sets the termios callback function.
There was a discussion about a similar proposed patch change. It was mentioned in the discussion that the reason set_termios hook was not set by default is because someone might be using a certain type of clock that can't handle rate rounding and ended up using improper clock frequency for some baud rates. See discussion thread here.
https://groups.google.com/forum/#!topic/fa.linux.kernel/oWrFOsw3rpQ
The current dw8250_set_termios is set such that it always call the standard serial8250_do_set_termios. So if there are clock frequency issues, this will be resolved in serial8250_do_set_termios.
This patchset has been tested on Cygnus VOIP board bcm911360_entphn board.
This patchset is based on v4.9-rc1
repo: https://github.com/Broadcom/cygnus-linux.git
branch: cygnus-tty-v1
Jason Uy (1):
serial: 8250_dw: Allow hardware flow control to be used
drivers/tty/serial/8250/8250_dw.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
--
1.9.1
next reply other threads:[~2016-12-06 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 22:34 Jason Uy [this message]
2016-12-06 22:34 ` [PATCH v1 1/1] " Jason Uy
2016-12-07 11:09 ` Andy Shevchenko
2017-01-11 8:00 ` Greg Kroah-Hartman
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=1481063643-11951-1-git-send-email-jason.uy@broadcom.com \
--to=jason.uy@broadcom.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=annie.wang@amd.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=noamc@ezchip.com \
--cc=wangkefeng.wang@huawei.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®