[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <49F6B782.8030205@euromail.se>
Date: Tue, 28 Apr 2009 10:00:02 +0200
From: Henrik Rydberg <rydberg@...omail.se>
To: Dmitry Torokhov <dmitry.torokhov@...il.com>
CC: Andrew Morton <akpm@...ux-foundation.org>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 6/6] input: Add a detailed multi-touch finger data report
protocol (rev2)
Dmitry Torokhov wrote:
> Hi Henrik,
>
> On Wed, Jan 28, 2009 at 11:23:49AM +0100, Henrik Rydberg wrote:
>> +
>> +#define ABS_MT_TOUCH 0x30 /* Diameter of touching circle */
>> +#define ABS_MT_TOUCH_MAJOR 0x30 /* Major axis of touching
>> ellipse */
>
> It looks like we are overriding the same event code to trasnmit 2
> slightly different kinds of data. I Am concerned that people would get
> confused, maybe we should get rid of ABS_MT_TOUCH and either require
> drvices always transmit ABS_MT_TOUCH_MAJOR and ABS_MT_TOUCH_MINOR or
> document that for curcular objects ABS_MT_TOUCH_MINOR may be omitted.
Done.
>> @@ -744,6 +758,14 @@ struct input_absinfo {
>> #define BUS_ATARI 0x1B
>>
>> /*
>> + * MT_TOOL types
>> + */
>> +#define MT_TOOL_FINGER 0
>> +#define MT_TOOL_PEN 1
>> +#define MT_TOOL_MAX 9
>> +#define MT_TOOL_CNT (MT_TOOL_MAX + 1)
>
> MT_TOOL_FINGER/MT_TOOL_PEN are documented values of ABS_MT_TOOL_TYPE, so
> I don't understand why we need MT_TOOL_MAX/MT_TOOL_CNT definitions.
Ah! It is a remnant from a much earlier version which used a separate MT
event type. It slipped through, my bad. Remedied. Thanks.
Revision three of the patch has been sent.
Cheers,
Henrik
--
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/
Powered by blists - more mailing lists