From: Jiri Slaby <jirislaby@kernel.org>
To: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: linux-serial@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Gilles Buloz <gilles.buloz@kontron.com>,
Johan Hovold <johan@kernel.org>
Subject: Re: [PATCH 1/2] tty: Add lookahead param to receive_buf
Date: Wed, 6 Apr 2022 10:07:31 +0200 [thread overview]
Message-ID: <cffdfa4c-57f8-a8f7-758e-2975b91d7b92@kernel.org> (raw)
In-Reply-To: <YkxoR+jA9tDJOqNU@smile.fi.intel.com>
On 05. 04. 22, 18:03, Andy Shevchenko wrote:
> On Tue, Apr 05, 2022 at 01:24:36PM +0300, Ilpo Järvinen wrote:
>> After lookahead for XON/XOFF characters is added by the next
>> patch, the receive side needs to ensure the flow-control
>> actions are not retaken later on when those same characters
>> get read by TTY.
>>
>> Thus, pass lookahead count to receive_buf and skip
>> flow-control character actions if already taken for the
>> character in question. Lookahead count will become live after
>> the next patch.
>
> ...
>
>> -static void n_tty_receive_char_special(struct tty_struct *tty, unsigned char c)
>> +static void n_tty_receive_char_special(struct tty_struct *tty, unsigned char c,
>> + bool lookahead_done)
>> {
>> struct n_tty_data *ldata = tty->disc_data;
>>
>> if (I_IXON(tty)) {
>> if (c == START_CHAR(tty)) {
>> - start_tty(tty);
>> - process_echoes(tty);
>> + if (!lookahead_done) {
>> + start_tty(tty);
>> + process_echoes(tty);
>> + }
>> return;
>> }
>> if (c == STOP_CHAR(tty)) {
>> - stop_tty(tty);
>> + if (!lookahead_done)
>> + stop_tty(tty);
>> return;
>> }
>
> Wouldn't be cleaner to inside out the conditionals?
Seconded.
> if (I_IXON(tty)) {
> if (lookahead_done) {
> // Can be joined, but I think this is better
I would join them, IMO it'd be still easy to read and to follow too.
> if (c == START_CHAR(tty))
> return;
> if (c == STOP_CHAR(tty))
> return;
> } else {
> if (c == START_CHAR(tty)) {
> start_tty(tty);
> process_echoes(tty);
> return;
> }
> if (c == STOP_CHAR(tty)) {
> stop_tty(tty);
> return;
> }
> }
> }
thanks,
--
js
suse labs
next prev parent reply other threads:[~2022-04-06 12:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 10:24 [PATCH 0/2] tty/serial: Process XON/XOFF robustly Ilpo Järvinen
2022-04-05 10:24 ` [PATCH 1/2] tty: Add lookahead param to receive_buf Ilpo Järvinen
2022-04-05 16:03 ` Andy Shevchenko
2022-04-06 8:07 ` Jiri Slaby [this message]
2022-04-06 8:13 ` Jiri Slaby
2022-04-06 8:46 ` Ilpo Järvinen
2022-04-05 10:24 ` [PATCH 2/2] tty: Implement lookahead to process XON/XOFF timely Ilpo Järvinen
2022-04-05 16:11 ` Andy Shevchenko
2022-04-06 8:21 ` Jiri Slaby
2022-04-06 8:50 ` Ilpo Järvinen
2022-04-06 8:54 ` Andy Shevchenko
2022-04-06 8:56 ` Andy Shevchenko
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=cffdfa4c-57f8-a8f7-758e-2975b91d7b92@kernel.org \
--to=jirislaby@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gilles.buloz@kontron.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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®