From: Laxman Dewangan <ldewangan@nvidia.com>
To: "Li, Aubrey" <aubrey.li@linux.intel.com>,
One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: "dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
"sachin.kamat@linaro.org" <sachin.kamat@linaro.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>
Subject: Re: [patch]GPIO button is supposed to wake the system up if the wakeup attribute is set
Date: Tue, 15 Apr 2014 18:08:03 +0530 [thread overview]
Message-ID: <534D282B.50301@nvidia.com> (raw)
In-Reply-To: <534C01DD.4010807@linux.intel.com>
On Monday 14 April 2014 09:12 PM, Li, Aubrey wrote:
> ping...
>
> On 2014/4/10 18:48, One Thousand Gnomes wrote:
>> On Thu, 10 Apr 2014 10:11:09 +0800
>> "Li, Aubrey" <aubrey.li@linux.intel.com> wrote:
>>
>>> When the wakeup attribute is set, GPIO button is supposed to set
>>> irqflag - IRQF_NO_SUSPEND to request irq. So when the system enters
>>> the suspend sleep mode, the GPIO irq keeps enabled and is able to
>>> wake the system up.
>>>
I think when we say irq_wake_enable() then based on underlying HW, it
should not turn off the irq if it is require for the wakeup. I mean it
need to be handle in the hw specific callbacks to keep enabling the
wakeup irq on suspend also.
For me, I have key which is interrupt based from PMIC, not based on GPIO
and on that if I set it to IRQF_EARLY_RESUME then it works fine.
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
next prev parent reply other threads:[~2014-04-15 12:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 2:11 [patch]GPIO button is supposed to wake the system up if the wakeup attribute is set Li, Aubrey
2014-04-10 10:48 ` One Thousand Gnomes
2014-04-14 15:42 ` Li, Aubrey
2014-04-15 12:38 ` Laxman Dewangan [this message]
2014-04-15 16:18 ` Li, Aubrey
2014-04-16 12:35 ` Laxman Dewangan
2014-04-17 16:42 ` Li, Aubrey
2014-04-17 17:18 ` Laxman Dewangan
2014-04-17 17:48 ` Li, Aubrey
2014-04-17 23:54 ` Dmitry Torokhov
2014-04-18 5:23 ` Li, Aubrey
2014-04-20 19:39 ` Dmitry Torokhov
2014-04-21 1:34 ` Li, Aubrey
2014-04-21 15:55 ` Dmitry Torokhov
2014-04-21 16:16 ` Li, Aubrey
2014-04-21 16:26 ` Dmitry Torokhov
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=534D282B.50301@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=aubrey.li@linux.intel.com \
--cc=dmitry.torokhov@gmail.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-input@vger.kernel.org \
--cc=sachin.kamat@linaro.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 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.