[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdbb0oeA0b5SSLtR6U7jv8asCeEJdHEsDAg7_tH+GHc5RQ@mail.gmail.com>
Date: Thu, 4 Sep 2014 18:27:11 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Soren Brinkmann <soren.brinkmann@...inx.com>
Cc: Alexandre Courbot <gnurou@...il.com>,
Michal Simek <michal.simek@...inx.com>,
Harini Katakam <harinik@...inx.com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
Lars-Peter Clausen <lars@...afoo.de>,
Ezra Savard <ezras@...inx.com>,
Ezra Savard <ezra.savard@...inx.com>
Subject: Re: [PATCH 2/3] gpio: zynq: Fixed broken wakeup implementation
On Fri, Aug 29, 2014 at 7:58 PM, Soren Brinkmann
<soren.brinkmann@...inx.com> wrote:
> From: Ezra Savard <ezra.savard@...inx.com>
>
> Use of unmask/mask in set_wake was an incorrect implementation. The new
> implementation correctly sets wakeup for the gpio chip's IRQ so the gpio chip
> will not sleep while wakeup-enabled gpio are in use.
>
> Signed-off-by: Ezra Savard <ezra.savard@...inx.com>
> Reviewed-by: Soren Brinkmann <soren.brinkmann@...inx.com>
Patch applied.
However the problems seems quite generic.
Do you see this kind of error in other GPIO drivers?
IRQchip semantics always make me nervous.
Yours,
Linus Walleij
--
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