From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wanlong Gao Subject: Re: [PATCH 6/6] Input: elantech - add v3 hardware support Date: Thu, 18 Aug 2011 14:06:29 +0800 Message-ID: <4E4CABE5.7020900@cn.fujitsu.com> References: <1313632629-23603-1-git-send-email-jj_ding@emc.com.tw> <1313632629-23603-7-git-send-email-jj_ding@emc.com.tw> <4E4C80A0.8090708@cn.fujitsu.com> <87d3g347ey.fsf@emc.com.tw> <4E4CA3A9.2010900@cn.fujitsu.com> <4E4CA6B4.5060807@cn.fujitsu.com> Reply-To: gaowanlong@cn.fujitsu.com Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from cn.fujitsu.com ([222.73.24.84]:63692 "EHLO song.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1750762Ab1HRGID (ORCPT ); Thu, 18 Aug 2011 02:08:03 -0400 In-Reply-To: Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Daniel Kurtz Cc: JJ Ding , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, Seth Forshee , Dmitry Torokhov , Aaron Huang , Tom Lin , Eric Piel , Chase Douglas , Henrik Rydberg , Alessandro Rubini On 08/18/2011 02:01 PM, Daniel Kurtz wrote: > On Thu, Aug 18, 2011 at 1:44 PM, Wanlong Gao wrote: >> On 08/18/2011 01:34 PM, Daniel Kurtz wrote: >>> >>> On Thu, Aug 18, 2011 at 1:31 PM, Wanlong Gao >>> wrote: >>>> >>>> On 08/18/2011 01:26 PM, JJ Ding wrote: >>>>> >>>>> Hi Wanlong Gao, >>>>> >>>>> On Thu, 18 Aug 2011 11:01:52 +0800, Wanlong >>>>> Gao >>>>> wrote: >>>>>> >>>>>> On 08/18/2011 09:57 AM, JJ Ding wrote: >>>>>>> >>>>>>> v3 hardware's packet format is almost identical to v2 (one/three >>>>>>> finger >>>>>>> touch), >>>>>>> except when sensing two finger touch, the hardware sends 12 bytes of >>>>>>> data. >>>>>>> >>>>>>> Signed-off-by: JJ Ding >>>>>>> --- >>>>>>> Documentation/input/elantech.txt | 104 ++++++++++++++++-- >>>>>>> drivers/input/mouse/elantech.c | 218 >>>>>>> ++++++++++++++++++++++++++++++++++--- >>>>>>> drivers/input/mouse/elantech.h | 11 ++ >>>>>>> 3 files changed, 303 insertions(+), 30 deletions(-) >>>>>>> >>>>>>> +static int determine_packet_v3(struct psmouse *psmouse) >>>>>> >>>>>> elantech_check_parity_v1 >>>>>> packet_simple_check_v2 >>>>>> determine_packet_v3 >>>>>> >>>>>> Why not consistent them? >>>>> >>>>> OK, how do these names sound to you? >>>>> >>>>> elantech_check_parity_v1 >>>>> elantech_packet_check_v2 >>>>> elantech_packet_check_v3 >>>>> >>>>> Thanks, >>>>> jj >>>> >>>> Yeah, sounds perfectly. >>> >>> Or just: >>> >>> elantech_packet_check_v1 >>> elantech_packet_check_v2 >>> elantech_packet_check_v3 >>> >>> :) >> >> Hmm... maybe they can go into an elantech_packet_check()? >> like: >> case 1: >> ... >> case 2: >> ... >> What do you think? ;) >> >> Thanks >> -Wanlong Gao > > Since we've already parsed the hardware type at this point, it seems > inefficient to parse it again inside another function. > I would prefer individual functions. > > Thanks, > -Daniel > Yeah, It makes sense. Thanks -Wanlong Gao