From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Hal Murray <murray+fedora@ip-64-139-1-69.sjc.megapath.net>
Cc: Peter Hurley <peter@hurleysoftware.com>,
Stanislaw Gruszka <sgruszka@redhat.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
linux-rt-users@vger.kernel.org
Subject: Re: locking changes in tty broke low latency feature
Date: Wed, 19 Feb 2014 23:35:11 +0000 [thread overview]
Message-ID: <20140219233511.2467cdc8@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <20140219230623.736E8406062@ip-64-139-1-69.sjc.megapath.net>
> gpsd uses TIOCMIWAIT to get a wakeup from a PPS signal connected to a modem
> control line. That path might have the same problem and/or some ideas on how
> to handle the data case.
TIOCMIWAIT should be fine. The data processing is deferred but very few
devices defer processing of modem change events.
Alan
next prev parent reply other threads:[~2014-02-19 23:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-18 9:38 locking changes in tty broke low latency feature Stanislaw Gruszka
2014-02-18 9:57 ` One Thousand Gnomes
2014-02-18 22:12 ` Peter Hurley
2014-02-19 13:03 ` Stanislaw Gruszka
2014-02-19 16:55 ` Grant Edwards
2014-02-19 17:38 ` Peter Hurley
2014-02-19 18:12 ` Grant Edwards
2014-02-19 18:42 ` Peter Hurley
2014-02-19 19:17 ` One Thousand Gnomes
2014-02-19 20:22 ` Peter Hurley
2014-02-19 21:42 ` One Thousand Gnomes
2014-02-20 2:19 ` Peter Hurley
2014-02-21 15:39 ` One Thousand Gnomes
2014-02-21 15:58 ` Peter Hurley
2014-02-21 16:31 ` Grant Edwards
2014-02-19 23:06 ` Hal Murray
2014-02-19 23:35 ` One Thousand Gnomes [this message]
2014-02-20 2:55 ` Peter Hurley
2014-02-20 4:16 ` Greg KH
2014-02-20 18:16 ` Peter Hurley
2014-02-20 19:33 ` Grant Edwards
2014-02-20 22:06 ` Peter Hurley
2014-02-23 22:33 ` Thomas Gleixner
2014-02-24 0:23 ` Peter Hurley
2014-02-24 13:23 ` One Thousand Gnomes
2014-02-24 15:44 ` Grant Edwards
2014-02-20 21:55 ` Hal Murray
2014-02-20 22:14 ` Grant Edwards
2014-02-21 15:43 ` One Thousand Gnomes
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=20140219233511.2467cdc8@alan.etchedpixels.co.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=murray+fedora@ip-64-139-1-69.sjc.megapath.net \
--cc=peter@hurleysoftware.com \
--cc=sgruszka@redhat.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;
as well as URLs for NNTP newsgroup(s).