Re: [PATCH 09/10] [RFC] ravb: Remove obsolete explicit clock handling for WoL

2017-10-17 Thread Geert Uytterhoeven
Hi Sergei, On Mon, Oct 16, 2017 at 10:17 PM, Sergei Shtylyov wrote: > On 10/16/2017 04:55 PM, Geert Uytterhoeven wrote: >> Currently, if Wake-on-LAN is enabled, the EtherAVB device's module clock >> is manually kept running during system suspend, to make sure

Re: [PATCH 09/10] [RFC] ravb: Remove obsolete explicit clock handling for WoL

2017-10-16 Thread Sergei Shtylyov
On 10/16/2017 04:55 PM, Geert Uytterhoeven wrote: Currently, if Wake-on-LAN is enabled, the EtherAVB device's module clock is manually kept running during system suspend, to make sure the device stays active. Since "soc: renesas: rcar-sysc: Keep wakeup sources active during system suspend",

Re: [PATCH 09/10] [RFC] ravb: Remove obsolete explicit clock handling for WoL

2017-10-16 Thread Niklas Söderlund
Hi Geert, On 2017-10-16 15:55:15 +0200, Geert Uytterhoeven wrote: > Currently, if Wake-on-LAN is enabled, the EtherAVB device's module clock > is manually kept running during system suspend, to make sure the device > stays active. > > Since "soc: renesas: rcar-sysc: Keep wakeup sources active

[PATCH 09/10] [RFC] ravb: Remove obsolete explicit clock handling for WoL

2017-10-16 Thread Geert Uytterhoeven
Currently, if Wake-on-LAN is enabled, the EtherAVB device's module clock is manually kept running during system suspend, to make sure the device stays active. Since "soc: renesas: rcar-sysc: Keep wakeup sources active during system suspend", this workaround is no longer needed. Hence remove all