[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMz4kuKb8g5dAu5WQ847CODtVgJQBa_svbeQGGDsYpCjipBp_g@mail.gmail.com>
Date: Fri, 9 Feb 2018 17:23:15 +0800
From: Baolin Wang <baolin.wang@...aro.org>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc: Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
stephen lu <lumotuwe@...il.com>,
Arvind Yadav <arvind.yadav.cs@...il.com>,
Joseph Lo <josephl@...dia.com>,
Kate Stewart <kstewart@...uxfoundation.org>,
Philippe Ombredanne <pombredanne@...b.com>,
Thomas Gleixner <tglx@...utronix.de>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
DTML <devicetree@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>,
Mark Brown <broonie@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH] Input: gpio_keys: Add level trigger support for GPIO keys
On 9 February 2018 at 14:39, Dmitry Torokhov <dmitry.torokhov@...il.com> wrote:
> On Thu, Feb 8, 2018 at 10:08 PM, Baolin Wang <baolin.wang@...aro.org> wrote:
>> On some platforms (such as Spreadtrum platform), the GPIO keys can only
>> be triggered by level type.
>
> How do you stop the interrupt from re-triggering as long as the key
> stays pressed?
We will set the level type irq handler as handle_level_irq(), in this
function, it will mask and ack the irq firstly.
--
Baolin.wang
Best Regards
Powered by blists - more mailing lists