Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755240Ab2JEJpH (ORCPT ); Fri, 5 Oct 2012 05:45:07 -0400 Received: from tw-mx2.synaptics.com.tw ([203.163.83.68]:18472 "EHLO tw-mx2.synaptics.com.tw" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755168Ab2JEJpE convert rfc822-to-8bit (ORCPT ); Fri, 5 Oct 2012 05:45:04 -0400 From: Alexandra Chin To: Dmitry Torokhov CC: Henrik Rydberg , Linux Kernel , Linux Input , Linus Walleij , Naveen Kumar Gaddipati , Mahesh Srinivasan , Alex Chang , "Scott Lin" , Christopher Heiny Subject: RE: [PATCH] Input: Add new driver into Input Subsystem for Synaptics DS4 touchscreen I2C devices Thread-Topic: [PATCH] Input: Add new driver into Input Subsystem for Synaptics DS4 touchscreen I2C devices Thread-Index: AQHNk/HhVA088HpSAk6VMBpKXya6/ZelpTiwgAFjI8CAAGvVgIABSqoA//+Mi4CAAkYfcA== Date: Fri, 5 Oct 2012 09:44:55 +0000 Message-ID: References: <20121003180121.GA4198@polaris.bitmath.org> <20121004065137.GA14217@core.coreip.homeip.net> In-Reply-To: <20121004065137.GA14217@core.coreip.homeip.net> Accept-Language: zh-TW, en-US Content-Language: zh-HK X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.14.51.94] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1627 Lines: 39 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/