[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CACRpkdavXPrFpGmva1Fp9KqDbGzsGd9r8qg2MyLnTBAy24KRZQ@mail.gmail.com>
Date: Thu, 13 Aug 2015 14:47:54 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Eduardo Valentin <edubezval@...il.com>
Cc: Alexandre Courbot <gnurou@...il.com>, ubrindis56@...il.com,
Fabio Estevam <fabio.estevam@...escale.com>,
Fabio Estevam <festevam@...il.com>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] gpio/mxc: mask gpio interrupts in suspend
On Wed, Aug 5, 2015 at 7:23 PM, Eduardo Valentin <edubezval@...il.com> wrote:
> From: Ulises Brindis <ubrindis56@...il.com>
>
> Currently in the FSL platform all GPIO interrupts in a bank are muxed
> into two GPIO lines to the GPC interrupt controller. In each GPIO bank
> GPIOs 0-15 are OR'ed into one GPC interrupt controller interrupt and 16-31
> are OR'ed into another. With the current code, if any of the 0-15 or
> 16-31 interrupts are marked as wakeup capable, all interrupts belonging
> to that sub-bank (either 0-15 or 16-31) will wake up the device. This is
> because interrupts are only being masked at the interrupt controller
> and not at the GPIO controller.
>
> This patch allows masking of GPIO interrupts at the GPIO controller during
> suspend if they have not been labeled wakeup capable. This patch uses
> preexisting IRQCHIP_MASK_ON_SUSPEND flag while initializing the GPIO
> interrupts to get the desired behavior.
>
> Cc: Linus Walleij <linus.walleij@...aro.org>
> Cc: Alexandre Courbot <gnurou@...il.com>
> Cc: linux-gpio@...r.kernel.org
> Cc: linux-kernel@...r.kernel.org
> Signed-off-by: Eduardo Valentin <edubezval@...il.com>
> Signed-off-by: Ulises Brindis <ubrindis56@...il.com>
Patch applied.
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