All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Onkalo Samu <samu.p.onkalo@nokia.com>, linux-input@vger.kernel.org
Subject: Re: Poll rate change and closing indication to polled input device
Date: Fri, 9 Oct 2009 19:10:12 +0100	[thread overview]
Message-ID: <20091009181012.GA21731@sirena.org.uk> (raw)
In-Reply-To: <20091009162717.GC1092@core.coreip.homeip.net>

On Fri, Oct 09, 2009 at 09:27:18AM -0700, Dmitry Torokhov wrote:
> On Fri, Oct 09, 2009 at 01:12:02PM +0100, Mark Brown wrote:

> > It'd be really good to have this control exposed to user space in a
> > standard fashion.

> I'll take the patches.

Yes, I was planning on doing some - I've got a touchscreen driver to do
soon and was hoping to have time to look at this while working on that
driver.

> >  Other devices that generate constant data rates like
> > touchscreens could also benefit from it, changing their output rate
> > depending on the needs of user space to give a power saving.

> Not sure if this belongs to the input core as such. It seems that what
> you want here is dynamic power-management which works on the level below
> input core (individual devices on particular buses).

It definitely needs to be implemented in the drivers but they need to
present an interface to userspace which seems best placed in the core to
factor out code and help make sure that the interface is standardised.

  reply	other threads:[~2009-10-09 18:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09 12:02 Poll rate change and closing indication to polled input device Onkalo Samu
2009-10-09 12:12 ` Mark Brown
2009-10-09 16:27   ` Dmitry Torokhov
2009-10-09 18:10     ` Mark Brown [this message]
2009-10-13  1:08       ` Dmitry Torokhov
2009-10-13  9:19         ` Mark Brown

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=20091009181012.GA21731@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=samu.p.onkalo@nokia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.