From: Johan Hovold <johan@kernel.org>
To: Florian Zumbiehl <florz@florz.de>
Cc: Johan Hovold <johan@kernel.org>, linux-usb@vger.kernel.org
Subject: usbserial: pl2303 tx xon/xoff flow control
Date: Thu, 17 May 2018 11:19:18 +0200 [thread overview]
Message-ID: <20180517091918.GG30172@localhost> (raw)
On Thu, May 17, 2018 at 10:29:14AM +0200, Johan Hovold wrote:
> On Thu, May 17, 2018 at 05:39:21AM +0200, Florian Zumbiehl wrote:
> > Now, I agree that signaling lack of support would be better in general, but
> > it does change what the code does for (still) unsupported cases. After all,
> > usbserial in general does not signal that it doesn't support IXON/IXANY,
> > but just pretends that it does. So, if there is a good reason why usbserial
> > ignores POSIX on this point, I would think that would still apply for the
> > remaining unsupported cases after partial support is implemented?!
>
> There are historical reasons for a lot of things, but that's not
> necessarily a reason to continue taking shortcuts.
But on second thought, I think your approach here makes sense. If
usbserial ever gains generic IXON support, we'd just fall back to the
line-discipline implementation whenever the control characters do no
match.
Just clean up some of the lengthy conditionals (e.g. using intermediate
bools), and mention why you implemented things the way you did in the
commit message.
Thanks,
Johan
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-05-17 9:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 9:19 Johan Hovold [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-05-21 8:45 usbserial: pl2303 tx xon/xoff flow control Johan Hovold
2018-05-18 13:16 Johan Hovold
2018-05-18 13:09 Johan Hovold
2018-05-18 4:06 Florian Zumbiehl
2018-05-18 4:06 Florian Zumbiehl
2018-05-17 8:29 Johan Hovold
2018-05-17 3:39 Florian Zumbiehl
2018-05-16 13:28 Johan Hovold
2018-05-14 3:15 Florian Zumbiehl
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=20180517091918.GG30172@localhost \
--to=johan@kernel.org \
--cc=florz@florz.de \
--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;
as well as URLs for NNTP newsgroup(s).