mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Jiri Slaby <jirislaby@kernel.org>
Cc: linux-serial <linux-serial@vger.kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Gilles Buloz <gilles.buloz@kontron.com>,
	Johan Hovold <johan@kernel.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Subject: Re: [PATCH 1/2] tty: Add lookahead param to receive_buf
Date: Wed, 6 Apr 2022 11:46:57 +0300 (EEST)	[thread overview]
Message-ID: <10263812-e52-9d8d-f9f0-75e5f0c85f60@linux.intel.com> (raw)
In-Reply-To: <7cb1cc42-ef98-cbbe-1779-107602747d07@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 2614 bytes --]

On Wed, 6 Apr 2022, Jiri Slaby wrote:

> On 05. 04. 22, 12:24, 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.
> ...
> > --- a/include/linux/tty_ldisc.h
> > +++ b/include/linux/tty_ldisc.h
> > @@ -224,11 +224,11 @@ struct tty_ldisc_ops {
> >   	 * The following routines are called from below.
> >   	 */
> >   	void	(*receive_buf)(struct tty_struct *tty, const unsigned char
> > *cp,
> > -			       const char *fp, int count);
> > +			       const char *fp, int count, int
> > lookahead_count);
> >   	void	(*write_wakeup)(struct tty_struct *tty);
> >   	void	(*dcd_change)(struct tty_struct *tty, unsigned int status);
> >   	int	(*receive_buf2)(struct tty_struct *tty, const unsigned char
> > *cp,
> > -				const char *fp, int count);
> > +				const char *fp, int count, int
> > lookahead_count);
> 
> Please always use unsigned if you don't expect negative numbers. count should
> be changed to unsigned in long term too.

Ok. I had just used the same types as there were previously. The types are 
a big mess, int and size_t conversions being done back and forth within 
that callchain for count. And now that you mentioned unsigned it 
seems that fp (flag ptr) is also inconsistent.

> > diff --git a/include/linux/tty_port.h b/include/linux/tty_port.h
> > index 58e9619116b7..1871a6a9cb00 100644
> > --- a/include/linux/tty_port.h
> > +++ b/include/linux/tty_port.h
> > @@ -39,7 +39,7 @@ struct tty_port_operations {
> >   };
> >     struct tty_port_client_operations {
> > -	int (*receive_buf)(struct tty_port *port, const unsigned char *, const
> > unsigned char *, size_t);
> > +	int (*receive_buf)(struct tty_port *port, const unsigned char *, const
> > unsigned char *, size_t, size_t);
> 
> Good, here it is unsigned and even of size_t size (I don't immediately see
> why, but OK).

You mean that the flag ptr is now unsigned char * (which I didn't even 
touch)?

Your comment leaves me to wonder though, what you now want for the 
lookahead count (the last arg), size_t or unsigned int? Lookahead count 
cannot be negative, and AFAICT, count neither because that would mean tty 
has to return some characters back :-).

...Maybe I'll do another patch post these fix ones to match/correct the 
types.

-- 
 i.

  reply	other threads:[~2022-04-06 11:47 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
2022-04-06  8:13   ` Jiri Slaby
2022-04-06  8:46     ` Ilpo Järvinen [this message]
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=10263812-e52-9d8d-f9f0-75e5f0c85f60@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=gilles.buloz@kontron.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --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®