From: Florian Echtler <floe@butterbrot.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, benjamin.tissoires@gmail.com,
rydberg@euromail.se, dh.herrmann@gmail.com
Subject: Re: [PATCH v3] add sur40 driver for Samsung SUR40 (aka MS Surface 2.0/Pixelsense)
Date: Mon, 11 Nov 2013 11:08:07 +0100 [thread overview]
Message-ID: <5280AC87.4020905@butterbrot.org> (raw)
In-Reply-To: <20131111073105.GA7645@core.coreip.homeip.net>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
Hello Dmitry,
On 11.11.2013 08:31, Dmitry Torokhov wrote:
> Hi Florian,
>
> On Wed, Nov 06, 2013 at 03:26:51PM +0100, Florian Echtler wrote:
>> +
>> + /* max value unknown, but major/minor axis
>> + * can never be larger than screen */
>> + input_set_abs_params(input_dev, ABS_MT_TOUCH_MAJOR,
>> + 0, SENSOR_RES_X, 0, 0);
>> + input_set_abs_params(input_dev, ABS_MT_TOUCH_MINOR,
>> + 0, SENSOR_RES_Y, 0, 0);
>
> If the range is unknown do we really want to specify min/max?
Geometrically speaking, these _are_ the min/max values. I can't say for
sure if the device has a cutoff threshold somewhere, but in terms of
geometric interpretation, I'd say this is correct.
> Also, does the patch below mess up or device or it still works?
I'll test this tomorrow (no access to SUR40 today). If everything works,
should I resubmit my patch with yours included or just tell you that
it's fine?
BR, Florian
--
SENT FROM MY DEC VT50 TERMINAL
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-11-11 10:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 14:26 [PATCH v3] add sur40 driver for Samsung SUR40 (aka MS Surface 2.0/Pixelsense) Florian Echtler
2013-11-08 21:37 ` Henrik Rydberg
2013-11-11 6:56 ` David Herrmann
2013-11-11 7:31 ` Dmitry Torokhov
2013-11-11 10:08 ` Florian Echtler [this message]
2013-11-11 10:27 ` Henrik Rydberg
2013-11-12 13:35 ` Florian Echtler
2013-11-16 11:45 ` Florian Echtler
2013-11-16 18:08 ` Henrik Rydberg
2013-11-18 14:50 ` Florian Echtler
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=5280AC87.4020905@butterbrot.org \
--to=floe@butterbrot.org \
--cc=benjamin.tissoires@gmail.com \
--cc=dh.herrmann@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.