From: Tony Lindgren <tony@atomide.com>
To: santosh shilimkar <santosh.shilimkar@oracle.com>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
Sekhar Nori <nsekhar@ti.com>,
Linux-OMAP <linux-omap@vger.kernel.org>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Roger Quadros <rogerq@ti.com>
Subject: Re: [PATCH] gpio: omap: fix irq triggering in smart-idle wakeup mode
Date: Fri, 15 Apr 2016 11:54:30 -0700 [thread overview]
Message-ID: <20160415185429.GU5995@atomide.com> (raw)
In-Reply-To: <571106F3.9070805@oracle.com>
* santosh shilimkar <santosh.shilimkar@oracle.com> [160415 08:22]:
> On 4/15/2016 2:26 AM, Grygorii Strashko wrote:
> >
> >Santosh, Tony, do you want me to perform any additional actions regarding this patch?
> >
> This patch should be run across family of SOCs to make
> sure wakeup works on all of those if not done already
Also, I'm not sure if we can just drop this code in question.
After this patch, what function updates the GPIO wkup_en registers
depending on enable_irq_wake()/disable_irq_wake()?
Regards,
Tony
next prev parent reply other threads:[~2016-04-15 18:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 10:52 [PATCH] gpio: omap: fix irq triggering in smart-idle wakeup mode Grygorii Strashko
2016-04-12 16:44 ` santosh shilimkar
2016-04-12 18:10 ` Grygorii Strashko
2016-04-13 19:31 ` Tony Lindgren
2016-04-15 8:32 ` Linus Walleij
2016-04-15 9:26 ` Grygorii Strashko
2016-04-15 15:21 ` Tony Lindgren
2016-04-15 15:21 ` santosh shilimkar
2016-04-15 18:54 ` Tony Lindgren [this message]
2016-04-18 15:57 ` Grygorii Strashko
2016-04-18 23:36 ` Tony Lindgren
2016-04-19 0:01 ` santosh shilimkar
2016-04-26 13:58 ` Linus Walleij
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=20160415185429.GU5995@atomide.com \
--to=tony@atomide.com \
--cc=gnurou@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=rogerq@ti.com \
--cc=santosh.shilimkar@oracle.com \
--cc=ssantosh@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).