HID: RFC: Would HID_QUIRK_HAS_SPECIAL_DRIVER make sense?

HID: RFC: Would HID_QUIRK_HAS_SPECIAL_DRIVER make sense?

[Stefan Achatz]

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