Re: [PATCH v3 0/3] renesas: irqchip: Use wakeup_path i.s.o. explicit clock handling

On 12/02/18 13:55, Geert Uytterhoeven wrote: > Hi all, > > If an interrupt controller in a Renesas ARM SoC is part of a Clock > Domain, and it is part of the wakeup path, it must be kept active during > system suspend. > > Currently this is handled in all interrupt controller drivers by >

Re: [PATCH v3 0/3] renesas: irqchip: Use wakeup_path i.s.o. explicit clock handling

On 12 February 2018 at 14:55, Geert Uytterhoeven wrote: > Hi all, > > If an interrupt controller in a Renesas ARM SoC is part of a Clock > Domain, and it is part of the wakeup path, it must be kept active during > system suspend. > > Currently this is handled in

[PATCH v3 0/3] renesas: irqchip: Use wakeup_path i.s.o. explicit clock handling

Hi all, If an interrupt controller in a Renesas ARM SoC is part of a Clock Domain, and it is part of the wakeup path, it must be kept active during system suspend. Currently this is handled in all interrupt controller drivers by explicitly increasing the use count of the module clock