From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: NeilBrown <neilb@suse.de>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
GTA04 owners <gta04-owner@goldelico.com>
Subject: Re: [PATCH] Input: gpio_keys: Make sure wake-up buttons work.
Date: Sat, 08 Nov 2014 01:49:06 +0100 [thread overview]
Message-ID: <23209922.Rp3elUvURv@vostro.rjw.lan> (raw)
In-Reply-To: <20141108110058.6c5217e3@notabene.brown>
[-- Attachment #1: Type: text/plain, Size: 1887 bytes --]
On Saturday, November 08, 2014 11:00:58 AM NeilBrown wrote:
> On Fri, 7 Nov 2014 15:45:07 -0800 Dmitry Torokhov <dmitry.torokhov@gmail.com>
> wrote:
>
> > Hi Neil,
> >
> > On Sat, Nov 08, 2014 at 10:37:07AM +1100, NeilBrown wrote:
> > >
> > >
> > > If a key is to be used for wake-up, we must not disable
> > > the interrupt during suspend.
> > >
> > > Signed-off-by: NeilBrown <neilb@suse.de>
> > >
> > > diff --git a/drivers/input/keyboard/gpio_keys.c b/drivers/input/keyboard/gpio_keys.c
> > > index 8c98e97f8e41..0b5e54ae343e 100644
> > > --- a/drivers/input/keyboard/gpio_keys.c
> > > +++ b/drivers/input/keyboard/gpio_keys.c
> > > @@ -526,6 +526,8 @@ static int gpio_keys_setup_key(struct platform_device *pdev,
> > > */
> > > if (!button->can_disable)
> > > irqflags |= IRQF_SHARED;
> > > + if (button->wakeup)
> > > + irqflags |= IRQF_NO_SUSPEND;
> >
> > No, enable_irq_wake() should be enough. I believe Rafael has fixed that
> > in the core, right?
> >
>
> Interesting... you seem to be right, but I was having wakeup problems until
> I added that patch.
This was a fairly recent change made in 3.18-rc1.
> I didn't test exhaustively, but the first time my device entered suspend, the
> gpio-key didn't wake it up. Subsequent suspends did...
>
> After I applied this patch, it would reliably wake up even on the first
> suspend.
>
> So there seems to be something wrong, but maybe it is more subtle.
>
> Is there a good reason why enable_irq_wake() is only called just as the
> device is being suspended, and why disable_irq_wake() is called on resume?
> To me it would make more sense to just enable it once (if required) and leave
> it enabled....
On some platforms it actually changes the configuration of interrupt
controllers in to a "suspend mode" which is not appropriate for run time
AFAICS.
> I'll see what I can find.
Yes, please.
Rafael
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-11-08 0:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 23:37 NeilBrown
2014-11-07 23:45 ` Dmitry Torokhov
2014-11-08 0:00 ` NeilBrown
2014-11-08 0:49 ` Rafael J. Wysocki [this message]
2014-11-08 5:17 ` NeilBrown
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=23209922.Rp3elUvURv@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=dmitry.torokhov@gmail.com \
--cc=gta04-owner@goldelico.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
/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®