lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 21 Nov 2017 11:18:04 +0800
From:   Chris Chiu <>
To:     Mika Westerberg <>
Cc:     Linus Walleij <>,
        Heikki Krogerus <>,
        Daniel Drake <>,
        Andy Shevchenko <>,,
        Linux Kernel <>
Subject: Re: [PATCH] pinctrl: intel: Initialize GPIO properly when used
 through irqchip

On Mon, Nov 20, 2017 at 11:19 PM, Mika Westerberg
<> 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 <>
> Reported-by: Chris Chiu <>
> Signed-off-by: Mika Westerberg <>
> ---
> 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

Tested-by: Chris Chiu <>

Powered by blists - more mailing lists