Re: [PATCH 2/6] gpio/omap: remove saved_wakeup field from struct gpio_bank

2012-02-27 Thread Kevin Hilman
Tarun Kanti DebBarma tarun.ka...@ti.com writes: There is no more need to have saved_wakeup. Instead we can use context.wake_en which holds the current wakeup enable register context. This also means that the read from wakeup enable register is not needed. Signed-off-by: Tarun Kanti DebBarma

Re: [PATCH 2/6] gpio/omap: remove saved_wakeup field from struct gpio_bank

2012-02-27 Thread DebBarma, Tarun Kanti
On Tue, Feb 28, 2012 at 5:20 AM, Kevin Hilman khil...@ti.com wrote: Tarun Kanti DebBarma tarun.ka...@ti.com writes: There is no more need to have saved_wakeup. Instead we can use context.wake_en which holds the current wakeup enable register context. This also means that the read from wakeup

[PATCH 2/6] gpio/omap: remove saved_wakeup field from struct gpio_bank

2012-02-23 Thread Tarun Kanti DebBarma
There is no more need to have saved_wakeup. Instead we can use context.wake_en which holds the current wakeup enable register context. This also means that the read from wakeup enable register is not needed. Signed-off-by: Tarun Kanti DebBarma tarun.ka...@ti.com --- drivers/gpio/gpio-omap.c |

Re: [PATCH 2/6] gpio/omap: remove saved_wakeup field from struct gpio_bank

2012-02-23 Thread Felipe Balbi
On Thu, Feb 23, 2012 at 05:40:27PM +0530, Tarun Kanti DebBarma wrote: There is no more need to have saved_wakeup. Instead we can use context.wake_en which holds the current wakeup enable register context. This also means that the read from wakeup enable register is not needed.