[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8762ckzve7.fsf@ti.com>
Date: Fri, 27 Apr 2012 15:01:52 -0700
From: Kevin Hilman <khilman@...com>
To: NeilBrown <neilb@...e.de>
Cc: Tony Lindgren <tony@...mide.com>,
Russell King <linux@....linux.org.uk>,
Samuel Ortiz <sameo@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>,
"Rafael J. Wysocki" <rjw@...k.pl>, linux-omap@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-pm@...r.kernel.org,
Santosh Shilimkar <santosh.shilimkar@...com>
Subject: Re: [PATCH 1/3] ARM: omap2+: set IRQCHIP_SKIP_SET_WAKE for INTC interrupts.
NeilBrown <neilb@...e.de> writes:
> On Thu, 26 Apr 2012 13:39:07 -0700 Kevin Hilman <khilman@...com> wrote:
>
>> NeilBrown <neilb@...e.de> writes:
>>
>> > All interrupts can wake-from-sleep (I think) so it should be
>> > permissible to call enable_irq_wake(). Setting this flag allows that.
>> >
>> > It is needed because without this, an interrupt which is delivered
>> > during late suspend will get ignored but will not cause suspend to
>> > abort.
>> > If enable_irq_wake() is called and succeeds, check_wakuep_irqs()
>> > will abort the suspend if the interrupt has fired.
>> >
>> > Signed-off-by: NeilBrown <neilb@...e.de>
>>
>> The name of this flag and the effect of setting it are somewhat
>> confusing (e.g. why does skipping set_wake suddenly make wakeups work.)
>> So I tried to make it clearer with a reworking of the changelog (below.)
>>
>> If I understood this correctly, and if you're OK with the updated
>> changelog, I'll queue this up for v3.5.
>>
>
> I'm very OK with your updated changelog - thanks. Filling in various bits
> that I didn't know and clarifies the rest :-)
Great, thanks.
Adding ack from Santosh (thanks!) and queuing for v3.5[1]
Kevin
[1] git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git for_3.5/pm-misc
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists