On Tue, Aug 18, 2015 at 2:56 PM, Thomas Gleixner wrote:
> On Tue, 18 Aug 2015, Rafael J. Wysocki wrote:
>> The original point was that if two wakeup interrupts happened at the same
>> time,
>> it would be kind of moot which one was the "real" wakeup, but now that I
>> think
>> about it, reportin
On Tue, 18 Aug 2015, Rafael J. Wysocki wrote:
> The original point was that if two wakeup interrupts happened at the same
> time,
> it would be kind of moot which one was the "real" wakeup, but now that I think
> about it, reporting the first one should be enough to catch suprious wakeups
> anyway
On Monday, August 17, 2015 10:59:15 PM Thomas Gleixner wrote:
> On Sat, 8 Aug 2015, Rafael J. Wysocki wrote:
> > On Thursday, August 06, 2015 08:47:04 PM Alexandra Yates wrote:
> > > Add a new IRQ flag named IRQD_WAKEUP_TRIGGERED. This flag is set
> > > when a given IRQ fires after it has been arm
On Sat, 8 Aug 2015, Rafael J. Wysocki wrote:
> On Thursday, August 06, 2015 08:47:04 PM Alexandra Yates wrote:
> > Add a new IRQ flag named IRQD_WAKEUP_TRIGGERED. This flag is set
> > when a given IRQ fires after it has been armed for system wakeup.
> > The flag is cleared before arming the IRQ fo
On Thursday, August 06, 2015 08:47:04 PM Alexandra Yates wrote:
> Add a new IRQ flag named IRQD_WAKEUP_TRIGGERED. This flag is set
> when a given IRQ fires after it has been armed for system wakeup.
> The flag is cleared before arming the IRQ for system wakeup
> during the next system suspend. Thi
5 matches
Mail list logo