public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mikkel Krautz <krautz@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, vojtech@suse.cz
Subject: Re: [PATCH] hid-core: Configurable USB HID Mouse Interrupt Polling Interval
Date: Sat, 18 Dec 2004 04:42:46 +0000	[thread overview]
Message-ID: <41C3B546.2040105@gmail.com> (raw)
In-Reply-To: <20041218012725.GB25628@kroah.com>

Greg KH wrote:

>On Sat, Dec 18, 2004 at 02:12:50AM +0000, Mikkel Krautz wrote:
>  
>
>>Hi!
>>
>>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.
>
>thanks,
>
>greg k-h
>
>  
>
I'm not too familiar with sysfs, so I really don't know.

The interval is set when the device is configured - that's only once.

Therefore I think a static value in Kconfig is fine. Wouldn't a sysfs 
entry be a little overkill for this?


Mikkel Krautz


  parent reply	other threads:[~2004-12-18  2:27 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 [this message]
2004-12-18  2:59     ` Greg KH
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=41C3B546.2040105@gmail.com \
    --to=krautz@gmail.com \
    --cc=greg@kroah.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