[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAB4CAwchVf2G0N+OtAxbHR0+Gwd2a8otM7PKyXykGuksV68Wuw@mail.gmail.com>
Date: Tue, 21 Nov 2017 11:18:04 +0800
From: Chris Chiu <chiu@...lessm.com>
To: Mika Westerberg <mika.westerberg@...ux.intel.com>
Cc: Linus Walleij <linus.walleij@...aro.org>,
Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
Daniel Drake <drake@...lessm.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
linux-gpio@...r.kernel.org,
Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] pinctrl: intel: Initialize GPIO properly when used
through irqchip
On Mon, Nov 20, 2017 at 11:19 PM, Mika Westerberg
<mika.westerberg@...ux.intel.com> wrote:
> When a GPIO is requested using gpiod_get_* APIs the intel pinctrl driver
> switches the pin to GPIO mode and makes sure interrupts are routed to
> the GPIO hardware instead of IOAPIC. However, if the GPIO is used
> directly through irqchip, as is the case with many I2C-HID devices where
> I2C core automatically configures interrupt for the device, the pin is
> not initialized as GPIO. Instead we rely that the BIOS configures the
> pin accordingly which seems not to be the case at least in Asus X540NA
> SKU3 with Focaltech touchpad.
>
> When the pin is not properly configured it might result weird behaviour
> like interrupts suddenly stop firing completely and the touchpad stops
> responding to user input.
>
> Fix this by properly initializing the pin to GPIO mode also when it is
> used directly through irqchip.
>
> Reported-by: Daniel Drake <drake@...lessm.com>
> Reported-by: Chris Chiu <chiu@...lessm.com>
> Signed-off-by: Mika Westerberg <mika.westerberg@...ux.intel.com>
> ---
> Chris, Daniel,
>
> Could you check that this still solves the issue and maybe provide your
> Tested-by? Thanks!
>
I've verified on X540NA here and it's working fine w/o any abnormal touchpad
stop.
Tested-by: Chris Chiu <chiu@...lessm.com>
Powered by blists - more mailing lists