From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Mikael Johansson <mikael.lars.johansson@axis.com>
Cc: linux-serial@vger.kernel.org, Mikael Starvik <starvik@axis.com>,
Jesper Nilsson <jespern@axis.com>,
Johan Adolfsson <johana@axis.com>
Subject: Re: artpec.c / serial_core.c hardware flow control problem
Date: Thu, 28 Jun 2012 17:24:21 +0100 [thread overview]
Message-ID: <20120628172421.4cb91ada@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <4FEC7857.6010006@axis.com>
On Thu, 28 Jun 2012 17:29:27 +0200
Mikael Johansson <mikael.lars.johansson@axis.com> wrote:
> Greetings,
>
> We have a problem with drivers/serial/artpec.c (Not yet in main tree)
> which uses hardware supported flow control (XON/XOFF). We do cfmakeraw()
> and tcsetattr() from userspace to set a termios struct where (c_iflag &
> IXON) is not set. The problem is that the call to tcsetattr() is not
> propagated down to serial_artpec_set_termios(), the reason being that
> uart_set_termios() doesn't think that IXON is a RELEVANT_IFLAG and
> returns prematurely instead of calling uart_change_speed -->
> ops->set_termios().
>
> Could this be fixed by making IXON a RELEVANT_IFLAG?:
That's actually insufficient for those cases - you can set the characters
used for things as well plus IXANY and IXOFF.
It's a stupid "optimisation" and the only reason I didn't get rid of it
before was in case it broke something else. Time for it to go.
So yeah - I'd just delete it.
If you are doing hardware XON/XOFF watch c_cc[VSTART] and c_cc[VSTOP].
Those control the symbol used for soft flow control.
Alan
next prev parent reply other threads:[~2012-06-28 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 15:29 artpec.c / serial_core.c hardware flow control problem Mikael Johansson
2012-06-28 16:24 ` Alan Cox [this message]
2012-06-29 15:16 ` Johan Adolfsson
2012-06-29 16:31 ` Alan Cox
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=20120628172421.4cb91ada@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jespern@axis.com \
--cc=johana@axis.com \
--cc=linux-serial@vger.kernel.org \
--cc=mikael.lars.johansson@axis.com \
--cc=starvik@axis.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