From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christopher Heiny Subject: Re: [RFC PATCH 0/1] input/touchscreen: Synaptics Touchscreen Driver Date: Tue, 23 Mar 2010 12:18:19 -0700 Message-ID: <4BA913FB.1000508@synaptics.com> References: <1269310058-10894-1-git-send-email-cheiny@synaptics.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from us-mx4.synaptics.com ([12.178.49.178]:13962 "EHLO us-mx4.synaptics.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752510Ab0CWTSW (ORCPT ); Tue, 23 Mar 2010 15:18:22 -0400 In-Reply-To: Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: =?ISO-8859-1?Q?Arve_Hj=F8nnev=E5g?= Cc: Dmitry Torokhov , Jean Delvare , Linux Kernel , Linux Input , Allie Xiong , William Manson On 03/22/2010 08:04 PM, Arve Hj=F8nnev=E5g wrote: > On Mon, Mar 22, 2010 at 7:07 PM, Christopher Heiny wrote: > ... >> There are two existing drivers for similar Synaptics devices in the >> current kernel tree (excluding the PS/2 touchpad driver). These are= : >> >> ./linux-2.6/drivers/input/mouse/synaptics_i2c.c >> A driver for the Exeda 15mm touchpad, written by Mike Rapoport >> and Igor Grinberg >> >> ./linux-2.6/drivers/staging/dream/synaptics_i2c_rmi.c >> A driver for the HTC Dream ClearPad, written by Arve Hj=F8nnev= =E5g >> >> >> We have not extended these drivers for a couple of reasons. First, = the >> two drivers are specific to particular Synaptics products, and it is= our >> desire to produce a general solution that takes advantage of the 'se= lf >> describing' features of products that use the RMI protocol. >> > > Do you plan to add platform data to align the reported touchscreen > data with the screen behind it, or do the new hardware allow the the > firmware handle this? In the past we even needed separate parameters > for different firmware versions (seen in > drivers/staging/dream/synaptics_i2c_rmi.h). Hi Arve, RMI4 touchscreens allow adjustment of the reported coordinate range (se= e=20 the F11_2D_Ctrl6..9 registers, page 48 of the current version of the=20 spec at http://www.synaptics.com/developers/manuals). Using this=20 feature, the device can be configured to report the same number of=20 positions on each axis as there are pixels on the display. We plan to make these settings accessible via sysfs, so that it can be=20 dynamically tweaked if the user changes the display resolution (not=20 likely on a phone, probable on a tablet/slate/ereader type device).=20 Assuming there are no significant issues with our current patch, we pla= n=20 to include that in the next one. We're holding off that implementation= =20 because we're still finding our feet on the submission process, and=20 wanted to keep the initial submits small so changes would be more=20 manageable. Coordinate rotation/reflection settings will be handled at the driver=20 level, again via sysfs. These features should be independent of the touchscreen firmware level.= =20 Initial settings for these features should probably be done at the=20 platform level. Chris -- To unsubscribe from this list: send the line "unsubscribe linux-input" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html