From: Ping Cheng <pinglinux@gmail.com>
To: Henrik Rydberg <rydberg@euromail.se>
Cc: linux-input@vger.kernel.org, dmitry.torokhov@gmail.com
Subject: Re: [PATCH] input : wacom - report resolution for ABS_MT events
Date: Fri, 28 Jan 2011 12:08:54 -0800 [thread overview]
Message-ID: <AANLkTikJt7So41PP06ac6JvsOg5L1tKLDYHzVzqsFzTP@mail.gmail.com> (raw)
In-Reply-To: <20110128191203.GA2729@polaris.bitmath.org>
On Fri, Jan 28, 2011 at 11:12 AM, Henrik Rydberg <rydberg@euromail.se> wrote:
>> >> This is mainly required by the serial pen and touch devices since
>> >> both pen and touch are on the same port. Updated the USB ones to
>> >> keep MT event definition consistent among serial and USB devices.
>> >
>> > Why is this change performed? What does the patch do? Please elaborate
>> > a little bit.
>>
>> Let's see if I can explain it clearer or not.
>>
>> We need to report resolution to userland for wacom_w8001.c.
>
> Thanks, perfect - sentences like this one is great to put in the patch
> description.
Thanks for the encouragement ;).
>> Since pen
>> and touch data are reported through the same logical port for serial
>> devices, using input_abs_set_res for ABS_X/Y, we can only pass the
>> resolution for pen or touch. So, I let ABS_X/Y report pen resolution
>> since most legacy ST clients process pen data over touch. However, for
>> multi-touch clients, especially for those that support gestures, touch
>> resolution is needed to calculate the physical distance between two
>> touch points. Using ABS_MT_POSITION_X/Y does not cause confusion and
>> it is quite intuitive.
>
> I thought this was solved by reporting both pen and touch on the same
> scale, which would render this problem moot. Or?
Yeah, see my reply to Dmitry for detail.
> [...]
>> > Is this for the BAMBOO_PT case? What about the extra x/y scaling for
>> > some of those devices?
>>
>> Yes, it is for Bamboo. We do not need to scale the value here since
>> touch and pen are on different ports. We had to scale the value for
>> wacom_w8001 since both pen and touch are on the same port. Without
>> scaling the data, the pen/finger tip will not follow the cursor on the
>> screen (wacom_w8001 is a touchscren device).
>
> I was thinking of the scaling quirk in effect for the Bamboo
> Touch. The resolution would have to change as well.
Yes, If we need to report the right values ;).
Ping
--
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
prev parent reply other threads:[~2011-01-28 20:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 1:47 [PATCH] input : wacom - report resolution for ABS_MT events Ping Cheng
2011-01-28 17:30 ` Henrik Rydberg
2011-01-28 18:23 ` Ping Cheng
2011-01-28 18:46 ` Dmitry Torokhov
2011-01-28 19:01 ` Ping Cheng
2011-01-28 19:37 ` Dmitry Torokhov
2011-01-28 20:08 ` Ping Cheng
2011-01-28 20:54 ` Dmitry Torokhov
2011-01-28 21:57 ` Ping Cheng
2011-01-29 0:05 ` Dmitry Torokhov
2011-01-29 6:19 ` Ping Cheng
2011-01-28 19:12 ` Henrik Rydberg
2011-01-28 20:08 ` Ping Cheng [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTikJt7So41PP06ac6JvsOg5L1tKLDYHzVzqsFzTP@mail.gmail.com \
--to=pinglinux@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=rydberg@euromail.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).