linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcin Slusarz <marcin.slusarz@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-input@vger.kernel.org
Subject: Re: [RFC PATCH 2/2] Add virtual "idle" device
Date: Thu, 12 Mar 2009 02:08:53 +0100	[thread overview]
Message-ID: <49B860A5.7020805@gmail.com> (raw)
In-Reply-To: <20090306184356.GA1311@ucw.cz>

Pavel Machek wrote:
> On Mon 2009-03-02 23:42:52, Marcin Slusarz wrote:
>> This virtual device can be used to tell user space about periods of time
>> when user didn't "touch" input devices (keyboards, mice, touchpads, joysticks,
>> etc). For now it supports only keyboard events.
>>
>> Notification is done through simple select/poll + ioctl interface.
>>
>> It can be used to implement screen savers, automatic suspend,
>> autoaway/autodisconnect (e.g. in instant messangers) without
>> any help from X server and its overhead (context switches).
> 
> I don't think this is good interface; what if you have more than one
> seat?

Good point. I haven't thought about it.
Moreover it wouldn't work with remote X sessions...

It could be used on single user systems (like laptops, personal desktops,
embedded), but user space couldn't know whether it safe to use it (maybe
excluding embedded).

> And without mouse handling it is useless anyway, so....

Well, I didn't want to dig too much into input layer just to
discover after patch submission that my core functionality is broken :).

Marcin


      reply	other threads:[~2009-03-12  1:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02 22:42 [RFC PATCH 2/2] Add virtual "idle" device Marcin Slusarz
2009-03-03 10:00 ` Geert Uytterhoeven
2009-03-03 14:17   ` Marcin Slusarz
2009-03-06 18:43 ` Pavel Machek
2009-03-12  1:08   ` Marcin Slusarz [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=49B860A5.7020805@gmail.com \
    --to=marcin.slusarz@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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).