From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: oskar.andero@sonyericsson.com
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jic23@cam.ac.uk" <jic23@cam.ac.uk>,
"aghayal@codeaurora.org" <aghayal@codeaurora.org>,
"Cavin, Courtney" <Courtney.Cavin@sonyericsson.com>
Subject: Re: [PATCH v3] input: add driver support for Sharp gp2ap002a00f proximity sensor
Date: Tue, 15 Nov 2011 10:29:10 -0800 [thread overview]
Message-ID: <20111115182909.GB6410@core.coreip.homeip.net> (raw)
In-Reply-To: <20111115125352.GA23767@caracas.corpusers.net>
On Tue, Nov 15, 2011 at 01:53:52PM +0100, oskar.andero@sonyericsson.com wrote:
> On 10:43 Tue 15 Nov , Dmitry Torokhov wrote:
> > On Tue, Nov 15, 2011 at 10:26:00AM +0100, oskar.andero@sonyericsson.com wrote:
> > > From: Courtney Cavin <courtney.cavin@sonyericsson.com>
> > > +
> > > +#ifdef CONFIG_PM_SLEEP
> > > +static int gp2a_suspend(struct device *dev)
> > > +{
> > > + struct i2c_client *client = to_i2c_client(dev);
> > > + struct gp2a_data *dt = i2c_get_clientdata(client);
> > > + int error;
> > > +
> > > + mutex_lock(&dt->device->mutex);
> > > +
> > > + if (dt->device->users) {
> > > + if (device_may_wakeup(&client->dev)) {
> > > + enable_irq_wake(client->irq);
> >
> > I think this part should happen regardless of whether device has users,
> > only non wakeup source case needs it.
>
> Hmm.. why would one want to enable irq_wake when there are no users?
> Wouldn't this cause the device to wakeup at every irq and report an
> switch event that no one listens to?
You are suspending the system and want to have this device as a wakeup
source. Note: not wake up _device_ at every IRQ but wake up the whole
_system_ when device generates an IRQ while system is asleep.
It does not matter whether there are users for the events; you
want the system to wake up.
At least this is the usual semantics.
--
Dmitry
next prev parent reply other threads:[~2011-11-15 18:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 9:26 oskar.andero
2011-11-15 9:43 ` Dmitry Torokhov
2011-11-15 12:53 ` oskar.andero
2011-11-15 18:29 ` Dmitry Torokhov [this message]
2011-11-16 10:37 ` oskar.andero
2011-11-16 11:28 ` Shubhrajyoti
2011-11-16 12:18 ` oskar.andero
2011-11-17 11:22 ` oskar.andero
2011-11-17 21:43 ` Dmitry Torokhov
2011-11-18 9:44 ` oskar.andero
2011-11-18 15:30 ` Shubhrajyoti
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=20111115182909.GB6410@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=Courtney.Cavin@sonyericsson.com \
--cc=aghayal@codeaurora.org \
--cc=jic23@cam.ac.uk \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oskar.andero@sonyericsson.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
all inboxes | Powered by JetHome®