Re: [PATCH v3 3/3] gpio: rcar: Use wakeup_path i.s.o. explicit clock handling

2018-03-02 Thread Linus Walleij
On Fri, Mar 2, 2018 at 9:20 AM, Geert Uytterhoeven wrote: > > On Thu, Mar 1, 2018 at 5:06 PM, Linus Walleij > wrote: >> On Mon, Feb 12, 2018 at 2:55 PM, Geert Uytterhoeven >> wrote: >> >>> Since commit ab82fa7da4dce5c7

Re: [PATCH v3 3/3] gpio: rcar: Use wakeup_path i.s.o. explicit clock handling

2018-03-02 Thread Geert Uytterhoeven
Hi Linus, On Thu, Mar 1, 2018 at 5:06 PM, Linus Walleij wrote: > On Mon, Feb 12, 2018 at 2:55 PM, Geert Uytterhoeven > wrote: > >> Since commit ab82fa7da4dce5c7 ("gpio: rcar: Prevent module clock disable >> when wake-up is enabled"), when a

Re: [PATCH v3 3/3] gpio: rcar: Use wakeup_path i.s.o. explicit clock handling

2018-03-01 Thread Linus Walleij
On Mon, Feb 12, 2018 at 2:55 PM, Geert Uytterhoeven wrote: > Since commit ab82fa7da4dce5c7 ("gpio: rcar: Prevent module clock disable > when wake-up is enabled"), when a GPIO is used for wakeup, the GPIO > block's module clock (if exists) is manually kept running during

Re: [PATCH v3 3/3] gpio: rcar: Use wakeup_path i.s.o. explicit clock handling

2018-02-22 Thread Geert Uytterhoeven
Hi Linus, On Thu, Feb 22, 2018 at 3:23 PM, Linus Walleij wrote: > On Mon, Feb 12, 2018 at 2:55 PM, Geert Uytterhoeven > wrote: > >> Since commit ab82fa7da4dce5c7 ("gpio: rcar: Prevent module clock disable >> when wake-up is enabled"), when a

Re: [PATCH v3 3/3] gpio: rcar: Use wakeup_path i.s.o. explicit clock handling

2018-02-22 Thread Linus Walleij
On Mon, Feb 12, 2018 at 2:55 PM, Geert Uytterhoeven wrote: > Since commit ab82fa7da4dce5c7 ("gpio: rcar: Prevent module clock disable > when wake-up is enabled"), when a GPIO is used for wakeup, the GPIO > block's module clock (if exists) is manually kept running during