linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Paul Mundt <lethal@linux-sh.org>,
	linux-input@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH] input: gpio_keys: Polling mode support.
Date: Tue, 28 Oct 2008 23:51:23 -0400	[thread overview]
Message-ID: <20081029035123.GB27906@anvil.corenet.prv> (raw)
In-Reply-To: <20081028101857.GA25523@linux-sh.org>

Hi Paul,

On Tue, Oct 28, 2008 at 07:18:57PM +0900, Paul Mundt wrote:
> Ping.
> 
> On Tue, Oct 21, 2008 at 05:38:16PM +0900, Paul Mundt wrote:
> > This implements an optional polling mode for the gpio_keys driver,
> > necessary for GPIOs that are not able to generate IRQs.
> > 
> > Polling mode is done device granular, and can not be toggled for
> > individual GPIOs in order to maintain simplicity. Platforms with both
> > IRQ capable and incapable GPIOs are required to register multiple
> > times, once for each case.
> > 
> >  
> > -	input_unregister_device(input);
> > +	if (pdata->polling)
> > +		input_unregister_polled_device(poll_dev);

You also need to do input_free_polled_device (but not input_free_device
 - yeah, I know, its confusing... The reason is that input_dev is
   refcounted while input_polled_dev is not).
> > +	else
> > +		input_unregister_device(poll_dev->input);
> >  

I also concerned with unconditionally polling INPUT_POLLDEV for all
users of gpio-keys. Maybe we could make polling support optional?

-- 
Dmitry

  reply	other threads:[~2008-10-29  3:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-21  8:38 [PATCH] input: gpio_keys: Polling mode support Paul Mundt
2008-10-28 10:18 ` Paul Mundt
2008-10-29  3:51   ` Dmitry Torokhov [this message]
2008-11-25 20:43     ` Paul Mundt
2008-12-08  3:32       ` Paul Mundt
2008-12-24  1:47         ` Paul Mundt
  -- strict thread matches above, loose matches on Subject: below --
2010-07-06 19:01 [PATCH] input: gpio_keys: polling " Alexander Clouter
2010-07-08 16:26 ` Alexander Clouter
2010-07-12 19:29 ` Alexander Clouter
2010-07-13  1:17   ` Paul Mundt
2010-07-13  1:28     ` Dmitry Torokhov
2010-07-13  7:26       ` Alexander Clouter

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=20081029035123.GB27906@anvil.corenet.prv \
    --to=dmitry.torokhov@gmail.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    /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).