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
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
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
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
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