[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091007043603.GC10204@core.coreip.homeip.net>
Date: Tue, 6 Oct 2009 21:36:04 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Pavel Machek <pavel@....cz>
Cc: rpurdie@...ys.net, lenz@...wisc.edu,
kernel list <linux-kernel@...r.kernel.org>,
Dirk@...er-Online.de, arminlitzel@....de,
Cyril Hrubis <metan@....cz>, thommycheck@...il.com,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
dbaryshkov@...il.com, omegamoon@...il.com, eric.y.miao@...il.com,
utx@...guin.cz, linux-input@...r.kernel.org,
"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: 32-rc1 aka 32-rc2: warning at manage.c:361 (set_irq_wake),
matrix-keypad related?
On Tue, Oct 06, 2009 at 09:58:17AM +0200, Pavel Machek wrote:
> Hi!
>
> On Mon 2009-10-05 22:06:50, Dmitry Torokhov wrote:
> > On Wed, Sep 30, 2009 at 10:07:46PM +0200, Pavel Machek wrote:
> > >
> > > It complains about unbalanced irq 113 wake disable. That one belongs
> > > to matrix-keypad...
> >
> > I guess some of enable_irq_wake()s fail on your box. Do you see it if
> > you apply the patch below?
>
> I'll do short test. But... if you are right, your patch will just make
> your machine refuse to suspend... right?
>
> Ungood.
It was just a debug patch.
>
> Actually, it seems to break suspend (returns -EINVAL while refusing
> to suspend), warnings are still there, and keyboard is dead after
> failed suspend... double plus ungood.
>
> Aha, so warning is solved: the one in the log is from gpio_buttons.
>
OK, so it looks like your box refuses to set up one of the GPIOs as a
wakeup source... Hmm, either your box is wrong ;) or matrix_keypad
driver needs to maintain a separate list of wakeup GPIOs.
--
Dmitry
--
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