On Mon, Jan 5, 2015 at 6:55 PM, Linus Walleij wrote:
>
> On Wed, Dec 31, 2014 at 9:55 PM, Linus Walleij
> wrote:
> > On Thu, Dec 11, 2014 at 2:02 PM, Octavian Purdila
> > wrote:
> >
> >> As noticed during suspend/resume operations, the IRQ can be unmasked
> >> then disabled in suspend and event
On Wed, Dec 31, 2014 at 9:55 PM, Linus Walleij wrote:
> On Thu, Dec 11, 2014 at 2:02 PM, Octavian Purdila
> wrote:
>
>> As noticed during suspend/resume operations, the IRQ can be unmasked
>> then disabled in suspend and eventually enabled in resume, but without
>> being unmasked.
>>
>> The curre
On Thu, Dec 11, 2014 at 2:02 PM, Octavian Purdila
wrote:
> As noticed during suspend/resume operations, the IRQ can be unmasked
> then disabled in suspend and eventually enabled in resume, but without
> being unmasked.
>
> The current implementation does not take into account interactions
> betwe
As noticed during suspend/resume operations, the IRQ can be unmasked
then disabled in suspend and eventually enabled in resume, but without
being unmasked.
The current implementation does not take into account interactions
between mask/unmask and enable/disable interrupts, and thus in the
above sc