From: Greg KH <greg@kroah.com>
To: Mikkel Krautz <krautz@gmail.com>
Cc: linux-kernel@vger.kernel.org, vojtech@suse.cz
Subject: Re: [PATCH] hid-core: Configurable USB HID Mouse Interrupt Polling Interval
Date: Fri, 17 Dec 2004 18:59:48 -0800 [thread overview]
Message-ID: <20041218025948.GB27152@kroah.com> (raw)
In-Reply-To: <41C3B546.2040105@gmail.com>
On Sat, Dec 18, 2004 at 04:42:46AM +0000, Mikkel Krautz wrote:
> Greg KH wrote:
> >On Sat, Dec 18, 2004 at 02:12:50AM +0000, Mikkel Krautz wrote:
> >>
> >>This patch adds the option "USB HID Mouse Interrupt Polling Interval"
> >>to drivers/usb/input/Kconfig, and a few lines of code to
> >>drivers/usb/input/hid-core.c, to make the config option function.
> >>
> >>It allows people to change the interval, at which their USB HID mice
> >>are polled at. This is extremely useful for people who require high
> >>precision, or just likes the feeling of a very precise mouse. ;)
> >>
> >>As the Kconfig help implies, setting a lower polling interval is known
> >>to work on several mice produced by Logitech and Microsoft. I only
> >>have a Logitech MX500 to test it on. My results have been positive,
> >>and so have many other people's.
> >
> >Why not just make it a sysfs file, so you can tune it per device? That
> >way you also don't have to make it a Kconfig option.
> >
> I'm not too familiar with sysfs, so I really don't know.
Poke around in it, I think it's the natural place for stuff like this.
> The interval is set when the device is configured - that's only once.
So it can never change? Why not add that feature at the same time?
> Therefore I think a static value in Kconfig is fine. Wouldn't a sysfs
> entry be a little overkill for this?
What about makeing it a module paramater then, that is exported to
sysfs? That makes it easier to adjust on the fly (before the mouse is
inserted), and doesn't require the kernel to be rebuilt.
Just trying to make things easier for users :)
thanks,
greg k-h
next prev parent reply other threads:[~2004-12-18 3:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-18 2:12 [PATCH] hid-core: Configurable USB HID Mouse Interrupt Polling Interval Mikkel Krautz
2004-12-18 0:43 ` Gene Heskett
2004-12-18 1:27 ` Greg KH
2004-12-18 4:22 ` Mikkel Krautz
2004-12-18 3:36 ` Gene Heskett
2004-12-18 4:42 ` Mikkel Krautz
2004-12-18 2:59 ` Greg KH [this message]
2004-12-18 4:55 ` Mikkel Krautz
2004-12-18 17:39 ` Mikkel Krautz
2004-12-18 15:40 ` Marcel Holtmann
2004-12-18 17:44 ` Mikkel Krautz
2004-12-18 16:53 ` Greg KH
2004-12-19 1:52 ` Mikkel Krautz
2005-02-06 19:07 ` Vojtech Pavlik
2005-02-06 20:00 ` Mikkel Krautz
-- strict thread matches above, loose matches on Subject: below --
2005-02-07 15:42 Mikkel Krautz
2005-02-07 15:44 Mikkel Krautz
2005-02-07 15:59 ` Randy.Dunlap
2005-02-07 17:16 ` Domen Puncer
2005-02-07 17:00 ` Randy.Dunlap
[not found] ` <20050207174303.GA3113@ucw.cz>
2005-02-07 17:51 ` Mikkel Krautz
2005-02-07 17:56 ` Mikkel Krautz
[not found] ` <20050207183818.GB2006@ucw.cz>
2005-02-07 18:41 ` Mikkel Krautz
2005-02-07 16:46 Mikkel Krautz
2005-02-07 18:57 Mikkel Krautz
2005-02-08 15:15 ` zyphr
2005-02-08 16:02 ` Oliver Neukum
2005-02-08 16:09 ` Vojtech Pavlik
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=20041218025948.GB27152@kroah.com \
--to=greg@kroah.com \
--cc=krautz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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