On Tue, Apr 21, 2015 at 7:27 PM, Semen Protsenko <semen.protsenko@xxxxxxxxxxxxxxx> wrote: > Set .irq_set_wake callback to prevent possible issues on wake-up. > > This patch was inspired by this commit: > b80eef95beb04760629822fa130aeed54cdfafca > > Signed-off-by: Semen Protsenko <semen.protsenko@xxxxxxxxxxxxxxx> Are these real, observed issues? Patch applied, but it seems we need a general approach to cover a few GPIO drivers with this kind of thing. Is this how we should always do it? Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 1/2] gpio: max732x: Propagate wake-up setting to parent irq controller
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH 1/2] gpio: max732x: Propagate wake-up setting to parent irq controller
- From: Linus Walleij <linus.walleij@xxxxxxxxxx>
- Date: Mon, 4 May 2015 15:32:31 +0200
- In-reply-to: <1429637257-11055-1-git-send-email-semen.protsenko@globallogic.com>
- Follow-Ups:
- References:
- [PATCH 1/2] gpio: max732x: Propagate wake-up setting to parent irq controller
- From: Semen Protsenko
- [PATCH 1/2] gpio: max732x: Propagate wake-up setting to parent irq controller
- Prev by Date: Re: [PATCH][V2] pinctrl: mediatek: mtk-common: initialize unmask
- Next by Date: [PATCH] gpio: rcar: Check for irq_set_irq_wake() failures
- Previous by thread: [PATCH 1/2] gpio: max732x: Propagate wake-up setting to parent irq controller
- Next by thread: Re: [PATCH 1/2] gpio: max732x: Propagate wake-up setting to parent irq controller
- Index(es):
 |