Message-ID: <4D7EEB64.5050402@seas.upenn.edu>
Date:	Tue, 15 Mar 2011 00:30:28 -0400
From:	Rafi Rubin <rafi@...s.upenn.edu>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
CC:	jkosina@...e.cz, linux-input@...r.kernel.org,
	linux-kernel@...r.kernel.org, micki@...rig.com,
	rydberg@...omail.se, chatty@...c.fr
Subject: Re: [PATCH 1/2] hid-ntrig: sysfs nodes for modes

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/13/11 01:27, Dmitry Torokhov wrote:
> On Fri, Mar 11, 2011 at 04:56:45AM -0500, Rafi Rubin wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> User desires aren't exactly my specialty.  I just know the ntrig windows control
>> panel gives the user that control with cute little radio buttons.
>>
>> Would it be cleaner to expose the control with an ioctrl or some other mechanism?
>>
>> I do have user space tools for mode and calibration, but that requires unbinding
>> the device, and just seems sloppier.  But if this really is inappropriate to add
>> the sysfs nodes, at least there's still some solution.
> 
> No, this is not inappropriate, I was just musing how useful they are. Do
> we foresee users really using them or if is it more "we export because we can".
> I.e. in which cases the default mode is not suitable?

Calibration is handy, I haven't counted how many users have asked for help and
calibrating fixed their problems.  It can be run with libusb from userspace, but
that requires unbinding the device and running more stuff with elevated
privileges.  X hotswap of input devices has improved, but transient settings are
still lost.  And of course we're still talking pain for any application that
uses the device directly but doesn't handle hotswap.


As for mode setting, I know I have used that feature through userspace and my
sysfs nodes.  But that doesn't mean other people care about that feature.
N-trig put it in the firmware and their windows control panel, perhaps Micki or
someone else from the company would care to weigh in on that.

>> Since you brought it up, I am thinking of removing some of the other nodes soon.
>>  I've learned the physical and logical ranges are already exposed both through
>> the event nodes and debugfs.  Also, I have better filtering that so far seems
>> not to need as many parameters so I should be able to remove those nodes as well.
>>
> 
> Well, that's the issue with sysfs - it really forms kernel ABI so
> removing something that was once added is hard.

Hm, sorry I was careless about that.  I was hoping for some feedback on the
tuning parameters and hoped to be able to remove some of those nodes once we
established good values.  Of course almost nobody actually used them and let me
know :(

Rafi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJNfuthAAoJEPILXytRLnK2brkP/1bj6+i+/umuuyJq58PBe8P1
+bagO7Rz2NUee7o++wdJSUW+GaL7lGLOySKi+gJ5N7vYHn7AekWT4lIUqjv0PinE
mnI2nhFqnWTyTGjbOFxazR4o6DG7YcdSmHDvLbqUOh7mJbfxZI9XqFLV7E+mCDpG
7VjtZMANq2Ju2/qr5B1h53WzvufEoXGhNIRyMpJbEaFAFjR0iG4UmTKNtsTPvNVt
knzZfkKk4VX+h72WgvvQ85/ViTLtBQXIU/AFNlgn3hysM+orA/OF1Rp0OX5aAz/p
rDQeJCYtP6GK1pzIbir2SS1tvnFfm+G2gxIDkBeh4ahL/x6z0D8EHl6rdZiodVeK
bxaXRQJh8cFTWMUDrySlzVf88ZQRvNVK8+bRcNXlqWnCDoY2xopPrVGBninZwvIs
laiWN64di1HVn7hgoy/iW/L2SA8NC9wQjd8X5TL9+EH0lToUvHxfqXooJzq31iwI
UuHPpVdyIeBTVl81zj+/cHWi4mEXnnjoANbjWOnTfFwDzDwaxop4/OwKhl4yebRM
t8ZJGPAJAzlse+FeuEd20P6kRvN7AUzBaG6Zwvyi9IRPfOPbsTF86jllNxJaEv4Y
ExuR6QZQ+HFRveojqhoHgD79nvgtQZlpVvIIggnsm0ImQ0pmSMMuhMjSb+Mna8c+
RfiTBxl9o6vVutQ4AkTk
=QQ0T
-----END PGP SIGNATURE-----
--
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