From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-input@vger.kernel.org
Subject: Re: O_ASYNC not working on /dev/input/event* ?
Date: Wed, 3 Feb 2010 23:09:25 -0800 [thread overview]
Message-ID: <20100204070925.GA7832@core.coreip.homeip.net> (raw)
In-Reply-To: <20100204070253.GB3928@atrey.karlin.mff.cuni.cz>
On Thu, Feb 04, 2010 at 08:02:53AM +0100, Pavel Machek wrote:
> > On Wed, Feb 03, 2010 at 09:56:00AM +0100, Pavel Machek wrote:
> > > HI!
> > >
> > > I'm trying to use O_ASYNC on /dev/input/event* (getting SIGIO when key
> > > is pressed), but so far no luck. Is it possible that O_ASYNC is not
> > > implemented there?
> >
> > You should be getting SIGIO when driver sends EV_SYN/SYN_REPORT...
>
> Thanks, it works now. Signal setup needs to be before fcntl().
>
Cool. Thanks for letting me know.
--
Dmitry
prev parent reply other threads:[~2010-02-04 7:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-03 8:56 O_ASYNC not working on /dev/input/event* ? Pavel Machek
2010-02-03 9:00 ` Dmitry Torokhov
2010-02-03 9:03 ` Dmitry Torokhov
2010-02-04 7:02 ` Pavel Machek
2010-02-04 7:09 ` Dmitry Torokhov [this message]
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=20100204070925.GA7832@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=pavel@ucw.cz \
/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).