[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdbpME+TErz=ZE0Sk9=R5comaU7A7Xo3YxVjqergp=n9MA@mail.gmail.com>
Date: Mon, 9 Dec 2013 11:15:36 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Chao Xu <caesarxuchao@...il.com>,
Kevin Hilman <khilman@...aro.org>,
"santosh.shilimkar@...com" <santosh.shilimkar@...com>
Cc: Linux-OMAP <linux-omap@...r.kernel.org>,
ext Kevin Hilman <khilman@...prootsystems.com>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
ext Tony Lindgren <tony@...mide.com>,
Felipe Balbi <balbi@...com>, Nishanth Menon <nm@...com>
Subject: Re: [RFC/RFT/PATCH V3] gpio: omap: refresh patch "be more aggressive
with pm_runtime" against v3.12-rc5
On Sun, Dec 8, 2013 at 5:40 AM, Chao Xu <caesarxuchao@...il.com> wrote:
> From: Felipe Balbi <balbi@...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@...il.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.]
> Signed-off-by: Chao Xu <caesarxuchao@...il.com>
Kevin/Santosh: you're maintainers for this driver, can you ACK/NACK
this patch?
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists