Re: [PATCH V2] gpio: omap: refresh patch "be more aggressive with pm_runtime" against v3.12-rc5

2013-12-02 Thread Chao Xu
Sorry for the late reply. On Fri, Nov 29, 2013 at 11:04 AM, Santosh Shilimkar wrote: > Adding Kevin's Linaro id, + Nishant, > > On Tuesday 26 November 2013 05:46 PM, Chao Xu wrote: >> From: Felipe Balbi >> >> try to keep gpio block suspended as much as possible. >> >> Tested with pandaboard and

Re: [PATCH V2] gpio: omap: refresh patch "be more aggressive with pm_runtime" against v3.12-rc5

2013-11-29 Thread Santosh Shilimkar
Adding Kevin's Linaro id, + Nishant, On Tuesday 26 November 2013 05:46 PM, Chao Xu wrote: > From: Felipe Balbi > > try to keep gpio block suspended as much as possible. > > Tested with pandaboard and a sysfs exported gpio. > > Signed-off-by: Felipe Balbi > > [caesarxuc...@gmail.com : Refresh

Re: [PATCH V2] gpio: omap: refresh patch "be more aggressive with pm_runtime" against v3.12-rc5

2013-11-29 Thread Linus Walleij
On Tue, Nov 26, 2013 at 11:46 PM, Chao Xu wrote: > From: Felipe Balbi > > try to keep gpio block suspended as much as possible. > > Tested with pandaboard and a sysfs exported gpio. > > Signed-off-by: Felipe Balbi > > [caesarxuc...@gmail.com : Refreshed against v3.12-rc5, and added revision >

Re: [PATCH V2] gpio: omap: refresh patch "be more aggressive with pm_runtime" against v3.12-rc5

2013-11-26 Thread Felipe Balbi
Hi, On Tue, Nov 26, 2013 at 04:46:44PM -0600, Chao Xu wrote: > From: Felipe Balbi > > try to keep gpio block suspended as much as possible. > > Tested with pandaboard and a sysfs exported gpio. > > Signed-off-by: Felipe Balbi > > [caesarxuc...@gmail.com : Refreshed against v3.12-rc5, and add

[PATCH V2] gpio: omap: refresh patch "be more aggressive with pm_runtime" against v3.12-rc5

2013-11-26 Thread Chao Xu
From: Felipe Balbi try to keep gpio block suspended as much as possible. Tested with pandaboard and a sysfs exported gpio. Signed-off-by: Felipe Balbi [caesarxuc...@gmail.com : Refreshed against v3.12-rc5, and added revision check to enable aggressive pm_runtime on OMAP4-only. Because am33x