[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdaZmU5Zpr3Tuq0LfXpoj4R7yvGd7COtzWCr3pPVs1j3DQ@mail.gmail.com>
Date: Mon, 29 May 2017 11:26:54 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc: "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
Hans de Goede <hdegoede@...hat.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Jarkko Nikula <jarkko.nikula@...ux.intel.com>,
Jagadish Krishnamoorthy <jagadish.krishnamoorthy@...el.com>
Subject: Re: [PATCH v2 10/12] PNP / ACPI: add support for GpioInt resource type
On Tue, May 23, 2017 at 7:03 PM, Andy Shevchenko
<andriy.shevchenko@...ux.intel.com> wrote:
> From: Jagadish Krishnamoorthy <jagadish.krishnamoorthy@...el.com>
>
> The PNP ACPI driver parses ACPI interrupt resource but not
> GpioInt resource. When the firmware passes GpioInt resource
> for IRQ the PNP ACPI driver ignores it and hence the interrupt for
> the particular driver will not work.
> One such example is 8042 keyboard which uses PNP driver for obtaining
> the interrupt resource. On Intel Braswell project GpioInt is used
> instead of interrupt resource and the keyboard driver fails to
> register interrupt.
> Fix the issue by parsing GpioInt resource type.
>
> Signed-off-by: Jagadish Krishnamoorthy <jagadish.krishnamoorthy@...el.com>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Fixed the paranthesis pointed out by Mika and applied
with his review tag.
Yours,
Linus Walleij
Powered by blists - more mailing lists