From: Yann Cantin <yann.cantin@laposte.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-input@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
dmitry.torokhov@gmail.com, jkosina@suse.cz
Subject: Re: [RFC ebeam PATCH 2/2] input: misc: New USB eBeam input driver
Date: Tue, 21 Jul 2015 14:18:39 +0200 [thread overview]
Message-ID: <55AE389F.9060409@laposte.net> (raw)
In-Reply-To: <20150720215956.GA21796@kroah.com>
Hi,
Le 20/07/2015 23:59, Greg KH a écrit :
> On Mon, Jul 20, 2015 at 11:03:19PM +0200, Yann Cantin wrote:
>> diff --git a/Documentation/ABI/testing/sysfs-driver-ebeam b/Documentation/ABI/testing/sysfs-driver-ebeam
>> +++ b/Documentation/ABI/testing/sysfs-driver-ebeam
>> @@ -0,0 +1,53 @@
>> +What: /sys/class/input/inputXX/device/min_x
>> + /sys/class/input/inputXX/device/min_y
>> + /sys/class/input/inputXX/device/max_x
>> + /sys/class/input/inputXX/device/max_y
>> +What: /sys/class/input/inputXX/device/h[1..9]
>> +What: /sys/class/input/inputXX/device/calibrated
>
>
> What tool(s) use these sysfs files? Don't we already have "normal"
> events for these types of things such that we don't have to make up new
> sysfs files for these?
The ebeam_calibrator tool is there : http://ebeam.tuxfamily.org.
I agree this can be a problem : this driver is totally useless without a
userspace dedicated calibration tool.
By nature these device's coordinate system can't be mapped to screen via
trivial transformations, such as scaling, flipping and rotating, hence the
special calibration and mapping procedures. I choose to use an homography
transformation as it is more robust and faster than linear interpolation
in this case. And anyway, it requires 9 calibration data and xy range
parameters.
I haven't found any existing tools performing that : xinput_calibrator
(witch ebeam_calibrator is based on) and other touchscreen calibration
tools can't do much more than trivial transformations.
>> +static DEVICE_ATTR(MM, S_IRUSR | S_IRGRP | S_IWUSR | S_IWGRP, \
>> + ebeam_##MM##_get, \
>> + ebeam_##MM##_set)
>
> DEVICE_ATTR_RW()?
Ok, will do.
>> + /* sysfs setup */
>> + err = sysfs_create_group(&intf->dev.kobj, &ebeam_attr_group);
>
> Ick, you just added the sysfs files to the USB device, not your input
> device, are you sure you tested this?
Yes, "run fine since 3.3.6, both x86_32 and 64.".
thanks,
--
Yann Cantin
A4FEB47F
--
next prev parent reply other threads:[~2015-07-21 12:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 21:03 [RFC ebeam PATCH 0/3] new USB eBeam input driver Yann Cantin
2015-07-20 21:03 ` [RFC ebeam PATCH 1/2] hid: Blacklist eBeam devices Yann Cantin
2015-07-20 21:03 ` [RFC ebeam PATCH 2/2] input: misc: New USB eBeam input driver Yann Cantin
2015-07-20 21:59 ` Greg KH
2015-07-20 22:26 ` Dmitry Torokhov
2015-07-20 22:40 ` Greg KH
2015-07-20 23:09 ` Dmitry Torokhov
2015-07-21 13:54 ` Yann Cantin
2015-07-21 12:18 ` Yann Cantin [this message]
2015-07-21 8:19 ` Oliver Neukum
2015-07-21 12:38 ` Yann Cantin
-- strict thread matches above, loose matches on Subject: below --
2013-07-24 23:52 [RFC ebeam PATCH 0/2] new " Yann Cantin
2013-07-24 23:52 ` [RFC ebeam PATCH 2/2] input: misc: New " Yann Cantin
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=55AE389F.9060409@laposte.net \
--to=yann.cantin@laposte.net \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jkosina@suse.cz \
--cc=linux-api@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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