[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdZvd_pApYbDL+PTJ1LDuDuvcVc2OCA_anRoWvwka_xm6g@mail.gmail.com>
Date: Wed, 12 Jun 2019 09:54:50 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Grygorii Strashko <grygorii.strashko@...com>
Cc: Russell King <rmk@....linux.org.uk>,
Tony Lindgren <tony@...mide.com>,
Bartosz Golaszewski <bgolaszewski@...libre.com>,
Linux-OMAP <linux-omap@...r.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Santosh Shilimkar <ssantosh@...nel.org>,
Russell King <rmk+kernel@...linux.org.uk>
Subject: Re: [PATCH-next 01/20] gpio: gpio-omap: ensure irq is enabled before wakeup
On Mon, Jun 10, 2019 at 7:11 PM Grygorii Strashko
<grygorii.strashko@...com> wrote:
> From: Russell King <rmk+kernel@...linux.org.uk>
>
> Documentation states:
>
> NOTE: There must be a correlation between the wake-up enable and
> interrupt-enable registers. If a GPIO pin has a wake-up configured
> on it, it must also have the corresponding interrupt enabled (on
> one of the two interrupt lines).
>
> Ensure that this condition is always satisfied by enabling the detection
> events after enabling the interrupt, and disabling the detection before
> disabling the interrupt. This ensures interrupt/wakeup events can not
> happen until both the wakeup and interrupt enables correlate.
>
> If we do any clearing, clear between the interrupt enable/disable and
> trigger setting.
>
> Signed-off-by: Russell King <rmk+kernel@...linux.org.uk>
> Signed-off-by: Grygorii Strashko <grygorii.strashko@...com>
Patch applied.
Yours,
Linus Walleij
Powered by blists - more mailing lists