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

Message-ID: <505A3FDD.1050006@synaptics.com>
Date:	Wed, 19 Sep 2012 14:57:49 -0700
From:	Christopher Heiny <cheiny@...aptics.com>
To:	Linus Walleij <linus.walleij@...aro.org>
CC:	Alexandra Chin <alexandra.chin@...synaptics.com>,
	Henrik Rydberg <rydberg@...omail.se>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>,
	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>
Subject: Re: [PATCH] Input: Add new driver into Input Subsystem for Synaptics
 DS4 touchscreen I2C devices

On 09/16/2012 03:33 PM, Linus Walleij wrote:
> On Sun, Sep 16, 2012 at 11:56 AM, Alexandra Chin
> <alexandra.chin@...synaptics.com> wrote:
>
>> Synaptics DS4 touchscreen driver implements a generic driver supporting I2C
>> protocol for Synaptics Design Studio 4 (DS4) family of Touchscreen Controllers
>> which include the following:
>>
>> - S32xX series
>> - S730X series
>> - S22xx series
>>
>> The driver supports multifinger pointing functionality and power management.
>> The driver is based on the original work submitted by
>> Linus Walleij <linus.walleij@...ricsson.com> and
>> Naveen Kumar Gaddipati <naveen.gaddipati@...ricsson.com>.
>
> Naveen's driver is sitting in drivers/staging/ste_rmi4 right now because
> Christopher Heiny is working on a RMI4 bus driver, and wanted to
> merge that.
>
> I am happy with this being merged for now if the plan is
> to eventually replace it with Christopher's (et al) driver,
> if it's not going to disturb the other driver in the end.
>
> How are Synaptics planning to handle the transition?
> (I assume you are coordinated... not always the case in
> big companies, I know from experience :-)
>
> Remember to keep Henrik Rydberg in the loop on touch
> controllers.

Hi Linus,

The RMI4 bus driver will continue to be developed by my team, with the 
intent that it will support all RMI4 functions as well as all Synaptics 
RMI4 products, and the goal of eventual inclusion in the kernel. 
However, as you've noted elsewhere, this is taking a while. :-)

In the meantime, there is a perceived customer pull for a limited 
functionality product/platform specific "thin driver".  Alexandra's team 
has been working on such a driver, resulting in her patch submission 
from a couple of days ago.  They really would like to see both our 
drivers being adopted into the kernel. This will enable them to support 
all our customers effectively and provide our customers with the best 
flexibility possible. Going forward, Synaptics will continue to 
maintain, support and upgrade these drivers for future touch controller 
platforms as well.

						Chris
--
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/