lists.openwall.net   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  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Sat, 14 Nov 2015 12:35:16 +0100
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Andrew Duggan <aduggan@...aptics.com>
Cc:	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	Benjamin Tissoires <benjamin.tissoires@...il.com>,
	Linux Input <linux-input@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@...hat.com>,
	Christopher Heiny <cheiny@...aptics.com>,
	Stephen Chandler Paul <cpaul@...hat.com>,
	Allie Xiong <axiong@...aptics.com>
Subject: Re: [PATCH 22/26] Input: synaptics-rmi4 - Add F30 support

On Wed, Nov 11, 2015 at 8:10 PM, Andrew Duggan <aduggan@...aptics.com> wrote:

> I don't know of any non touchpad devices which use F30 and I think it's
> unlikely that there would be any. I think it's really meant for controlling
> the buttons and LEDs which are on the touchpad PCB. There probably isn't
> much reason to wire external GPIOs and LEDs to be controlled by our ASIC*.
> If such a device existed then exporting GPIOs with gpio_chip and using
> gpio-keys seems like a reasonable way to do it. I'm just not sure we will
> have devices which need to use that implementation.
>
> * There is the one exception which is the Lenovo systems which have the
> external physical stick buttons are wired to our ASIC, but that is a special
> case and it's events should be forwarded to the stick's input device instead
> of being reported separately using gpio-keys.

We are aligned here.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ