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:	Fri, 6 May 2016 11:29:14 -0700
From:	Grant Grundler <grundler@...omium.org>
To:	Nicolas Ferre <nicolas.ferre@...el.com>
Cc:	Grant Grundler <grundler@...omium.org>,
	Rob Herring <robh@...nel.org>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	linux-input <linux-input@...r.kernel.org>,
	Grant Likely <grant.likely@...aro.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Linux DeviceTree <devicetree@...r.kernel.org>,
	Hung-yu Wu <hywu@...gle.com>
Subject: Re: Input: add Atmel Atmegaxx captouch driver

On Fri, May 6, 2016 at 2:19 AM, Nicolas Ferre <nicolas.ferre@...el.com> wrote:
...
> Is it different from the Atmel QT1070 or QT2160 which have drivers
> already available in Linux:  drivers/input/keyboard/qt1070.c

Yes.  What Daniel said.  I would describe it as "probe code and
interrupt handling protocol are different" from both qt1070 and
qt2160.

I'll add qt2160 is quite a bit more complex by adding LED driver
support in a separate work handler and can handle a matrix of key
codes. So very different protocol and linux device driver.

cheers,
grant

Powered by blists - more mailing lists