aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/hid
diff options
context:
space:
mode:
authorJindrich Makovicka <makovick@gmail.com>2010-06-03 06:50:42 -0400
committerJiri Kosina <jkosina@suse.cz>2010-06-04 05:19:02 -0400
commite5a2a04c264e693eafcc78fec5add34c9e15e471 (patch)
treeb1f2c82237aee7a2790b40d104261ab967e2fb4e /drivers/hid
parentfdd45ef44cfe84037f44ab386915b55c32a58bf7 (diff)
HID: check for HID_QUIRK_IGNORE during probing
While the hardcoded ignore list is checked in hid_add_device(), the user supplied ignore flags are not. Thus, the IGNORE quirk (0x0004) cannot be used to stop usbhid from binding devices like iBuddy, which has been recently removed from the ignore list due to product ID conflict. This patch adds the user quirk check to hid_add_device(), and makes hid_add_device() return -ENODEV when HID_QUIRK_IGNORE bit is set. HID_QUIRK_NO_IGNORE still takes precedence over HID_QUIRK_IGNORE. With the patch, iBuddy works properly using libusb when the following option is added to modprobe.d: options usbhid quirks=0x1130:0x0002:0x0004 Signed-off-by: Jindrich Makovicka <makovick@gmail.com> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
Diffstat (limited to 'drivers/hid')
-rw-r--r--drivers/hid/hid-core.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c
index aa0f7dcabcd7..66abeccdea78 100644
--- a/drivers/hid/hid-core.c
+++ b/drivers/hid/hid-core.c
@@ -1760,7 +1760,8 @@ int hid_add_device(struct hid_device *hdev)
1760 1760
1761 /* we need to kill them here, otherwise they will stay allocated to 1761 /* we need to kill them here, otherwise they will stay allocated to
1762 * wait for coming driver */ 1762 * wait for coming driver */
1763 if (!(hdev->quirks & HID_QUIRK_NO_IGNORE) && hid_ignore(hdev)) 1763 if (!(hdev->quirks & HID_QUIRK_NO_IGNORE)
1764 && (hid_ignore(hdev) || (hdev->quirks & HID_QUIRK_IGNORE)))
1764 return -ENODEV; 1765 return -ENODEV;
1765 1766
1766 /* XXX hack, any other cleaner solution after the driver core 1767 /* XXX hack, any other cleaner solution after the driver core