Messages in this thread | | | Subject | RE: [v3 1/3] 1/3 Touchscreen: Cypress TTSP G3 MTDEV Core Driver | Date | Mon, 3 Jan 2011 12:50:10 -0800 | From | "Kevin McNeely" <> |
| |
Hi Henrik,
The market we are currently servicing requires Protocol A and we are trying to meet those submission requirements in the near term.
With Protocol A available to the market, we will immediately work on a Protocol B driver which will take advantage of track id information that our device can provide. For that effort, I would sincerely appreciate information about testing (in-kernel tracking module?).
Thank you and best regards, Kevin
> -----Original Message----- > From: Henrik Rydberg [mailto:rydberg@euromail.se] > Sent: Monday, January 03, 2011 10:46 AM > To: Kevin McNeely > Cc: Dmitry Torokhov; David Brown; Trilok Soni; Samuel Ortiz; Eric Miao; > Mike Frysinger; Alan Cox; linux-input@vger.kernel.org; linux- > kernel@vger.kernel.org > Subject: Re: [v3 1/3] 1/3 Touchscreen: Cypress TTSP G3 MTDEV Core > Driver > > > > If the in-kernel tracking module was in place, would you consider > > > switching to the slots protocol? > > > > Hi Henrik, can you please clarify? Should I remove MTDEV from the > patch > > title? > > Let me start over - is there a way to reliably track contacts from the > device? If yes, the question is whether you would consider switching > to type B right away. If no, the question was whether you would > consider a switch to type B if there was a in-kernel tracking module > to use. I understand if there are other reasons to stay with type A, I > am mostly curious. > > And perhaps MTDEV is a bit misplaced in the title, unless it has > something to do with the device. > > Thanks, > Henrik
--------------------------------------------------------------- This message and any attachments may contain Cypress (or its subsidiaries) confidential information. If it has been received in error, please advise the sender and immediately delete this message. ---------------------------------------------------------------
| |