Linux Input/HID development
 help / color / mirror / Atom feed
From: Stefan Achatz <erazor_de@users.sourceforge.net>
To: linux-input@vger.kernel.org
Subject: HID: RFC: Would HID_QUIRK_HAS_SPECIAL_DRIVER make sense?
Date: Sun, 10 Nov 2013 15:32:06 +0100	[thread overview]
Message-ID: <1384093926.5711.64.camel@neuromancer.tessier-ashpool> (raw)

Hello,

devices that have special drivers in the kernel are added to
hid_core.c:hid_have_special_driver[] so that the hid-generic driver does
not bind the device.

Drivers not in the kernel have to rely on a mechanism of unbinding the
device from hid-generic and binding it to the right driver with an udev
rule or something.

I realized that on some modern distributions (namely Ubuntu13.10 and
Fedora19) this seems not to work anymore for my Roccat drivers. After
rebinding the device to the target driver the /dev/input/event* devices
show no output.
In Ubuntu13.10 this problem can be bypassed by adding the target module
to initrd, but not on Fedora19.

While I'm further investigating this issue it doesn't look like a basic
kernel problem, as the newer kernel versions work on older distros
flawlessly.

But I stumbled over the following idea which does not fix the problem,
but be an alternative to rebinding:

What about a HID_QUIRK_HAS_SPECIAL_DRIVER quirk that has the same
functionality as an entry in hid_have_special_driver[]?

In my eyes it looks like a suitable accommodation to the existing quirks
NOGET and IGNORE.

Mabe I'm overlooking something and a solution already exists?

Also, I would be glad to hear any hints on the rebind issue.

Thanks and have a nice day 
Stefan Achatz



                 reply	other threads:[~2013-11-10 14:32 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1384093926.5711.64.camel@neuromancer.tessier-ashpool \
    --to=erazor_de@users.sourceforge.net \
    --cc=linux-input@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