linux-kernel - RE: [PATCH] Input: Add new driver into Input Subsystem for Synaptics DS4 touchscreen I2C devices

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CC51EC7B5B7F984AA566DC102237848896F59949@hkdcw-mail1.synaptics-inc.local>
Date:	Fri, 5 Oct 2012 09:44:55 +0000
From:	Alexandra Chin <alexandra.chin@...synaptics.com>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
CC:	Henrik Rydberg <rydberg@...omail.se>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Linux Input <linux-input@...r.kernel.org>,
	Linus Walleij <linus.walleij@...ricsson.com>,
	Naveen Kumar Gaddipati <naveen.gaddipati@...ricsson.com>,
	Mahesh Srinivasan <msrinivasan@...aptics.com>,
	Alex Chang <alex.chang@...synaptics.com>,
	"Scott Lin" <scott.lin@...synaptics.com>,
	Christopher Heiny <Cheiny@...aptics.com>
Subject: RE: [PATCH] Input: Add new driver into Input Subsystem for
 Synaptics DS4 touchscreen I2C devices

Hi Dmitry/Henrik,


From: Dmitry Torokhov
Sent: Thursday, October 04, 2012 2:52 PM
> Given that the other group at Synaptics works on general version of RMI4
> driver what is the benefit of having separate driver for DS4 line? I can
> understand keeping one copy of older driver in staging so that some
> customers coudl still use hardware while universal implementation is
> being developed, but I do not see why we would want to have 3 separate
> drivers.


Thank you for your suggestions and comments!

We agree with your opinion. We will submit the driver as a patch on top 
of STE's driver since it is in the staging.

And we would like to state our purpose clearly why we are doing this 
including the following:
- We have customers that require a Touch Controller platform specific
 driver, that is protocol specific, following a single source file structure.
- There is also a requirement that the platform specific driver has to be 
 adopted and included into the Linux kernel.

As you are aware, Chris' team is working on general version of RMI4. 
However customers still require a platform specific driver for Touch 
Controller platform. We really hope both drivers (general RMI4 driver 
and STE's driver) being adopted into the kernel. This will allow us to 
provide the best flexibility possible to customers.

Your opinion will be greatly appreciated.

Alexandra Chin
--
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/