From: Konstantin Shkolnyy <konstantin.shkolnyy@gmail.com>
To: johan@kernel.org
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Konstantin Shkolnyy <konstantin.shkolnyy@gmail.com>
Subject: [PATCH v2 3/3] USB: serial: cp210x: Cleaned up CRTSCTS flag code.
Date: Fri, 29 Apr 2016 21:22:35 -0500 [thread overview]
Message-ID: <1461982955-19699-1-git-send-email-konstantin.shkolnyy@gmail.com> (raw)
The CRTSCTS flag code cleared (and inconsistently) bits unrelated to
CRTSCTS functionality. It was also harder than necessary to read.
Signed-off-by: Konstantin Shkolnyy <konstantin.shkolnyy@gmail.com>
---
Changes in v2:
Improved CRTSCTS fix based on feedback. Dropped get_termios error handling.
drivers/usb/serial/cp210x.c | 23 ++++++++++-------------
1 file changed, 10 insertions(+), 13 deletions(-)
diff --git a/drivers/usb/serial/cp210x.c b/drivers/usb/serial/cp210x.c
index da0567c..d3e1dd2 100644
--- a/drivers/usb/serial/cp210x.c
+++ b/drivers/usb/serial/cp210x.c
@@ -988,24 +988,21 @@ static void cp210x_set_termios(struct tty_struct *tty,
dev_dbg(dev, "%s - read ulControlHandshake=%08x ulFlowReplace=%08x\n",
__func__, ControlHandshake, FlowReplace);
+ ControlHandshake &= ~SERIAL_DSR_HANDSHAKE;
+ ControlHandshake &= ~SERIAL_DCD_HANDSHAKE;
+ ControlHandshake &= ~SERIAL_DSR_SENSITIVITY;
+ ControlHandshake &= ~SERIAL_DTR_MASK;
+ ControlHandshake |= SERIAL_DTR_ACTIVE;
if (cflag & CRTSCTS) {
- ControlHandshake &= ~(SERIAL_DTR_MASK |
- SERIAL_CTS_HANDSHAKE | SERIAL_DSR_HANDSHAKE |
- SERIAL_DCD_HANDSHAKE | SERIAL_DSR_SENSITIVITY);
- ControlHandshake |= SERIAL_DTR_ACTIVE;
ControlHandshake |= SERIAL_CTS_HANDSHAKE;
- /* FIXME why clear bits unrelated to flow control */
- /* FIXME why clear _XOFF_CONTINUE which is never set */
- FlowReplace &= ~0xffffffff;
+
+ FlowReplace &= ~SERIAL_RTS_MASK;
FlowReplace |= SERIAL_RTS_FLOW_CTL;
dev_dbg(dev, "%s - flow control = CRTSCTS\n", __func__);
} else {
- ControlHandshake &= ~(SERIAL_DTR_MASK |
- SERIAL_CTS_HANDSHAKE | SERIAL_DSR_HANDSHAKE |
- SERIAL_DCD_HANDSHAKE | SERIAL_DSR_SENSITIVITY);
- ControlHandshake |= SERIAL_DTR_ACTIVE;
- /* FIXME - why clear bits unrelated to flow control */
- FlowReplace &= ~0xff;
+ ControlHandshake &= ~SERIAL_CTS_HANDSHAKE;
+
+ FlowReplace &= ~SERIAL_RTS_MASK;
FlowReplace |= SERIAL_RTS_ACTIVE;
dev_dbg(dev, "%s - flow control = NONE\n", __func__);
}
--
1.8.4.5
reply other threads:[~2016-04-30 2:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1461982955-19699-1-git-send-email-konstantin.shkolnyy@gmail.com \
--to=konstantin.shkolnyy@gmail.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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®