From: Felipe Balbi <balbi@ti.com>
To: Chao Xu <caesarxuchao@gmail.com>
Cc: <linux-omap@vger.kernel.org>, <santosh.shilimkar@ti.com>,
<khilman@deeprootsystems.com>, <linus.walleij@linaro.org>,
<linux-gpio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<tony@atomide.com>, <balbi@ti.com>
Subject: Re: [PATCH V2] gpio: omap: refresh patch "be more aggressive with pm_runtime" against v3.12-rc5
Date: Tue, 26 Nov 2013 17:07:38 -0600 [thread overview]
Message-ID: <20131126230738.GA17630@saruman.home> (raw)
In-Reply-To: <1385506004-14943-1-git-send-email-caesarxuchao@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
Hi,
On Tue, Nov 26, 2013 at 04:46:44PM -0600, Chao Xu wrote:
> From: Felipe Balbi <balbi@ti.com>
>
> try to keep gpio block suspended as much as possible.
>
> Tested with pandaboard and a sysfs exported gpio.
>
> Signed-off-by: Felipe Balbi <balbi at ti.com>
>
> [caesarxuchao@gmail.com : Refreshed against v3.12-rc5, and added
> revision check to enable aggressive pm_runtime on OMAP4-only. Because
> am33xx_gpio_sysc.idlemodes seems to be wrongly marked as
> SIDLE_SMART_WKUP, which might cause missed interrupts with this patch.
> Tested on Pandaboard rev A2.]
Based on a quick look, it looks good to my eyes. Didn't test on any HW
though.
Signed-of-by: Felipe Balbi <balbi@ti.com>
> Signed-off-by: Chao Xu <caesarxuchao@gmail.com>
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-11-26 23:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 22:46 [PATCH V2] gpio: omap: refresh patch "be more aggressive with pm_runtime" against v3.12-rc5 Chao Xu
2013-11-26 23:07 ` Felipe Balbi [this message]
2013-11-29 10:05 ` Linus Walleij
2013-11-29 17:04 ` Santosh Shilimkar
2013-12-02 23:00 ` Chao Xu
2013-12-08 4:40 ` [RFC/RFT/PATCH V3] " Chao Xu
2013-12-09 10:15 ` Linus Walleij
2013-12-09 16:03 ` Kevin Hilman
2013-12-12 18:19 ` Linus Walleij
2013-12-12 18:28 ` Felipe Balbi
2013-12-12 18:38 ` 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=20131126230738.GA17630@saruman.home \
--to=balbi@ti.com \
--cc=caesarxuchao@gmail.com \
--cc=khilman@deeprootsystems.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=santosh.shilimkar@ti.com \
--cc=tony@atomide.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