HID: generic: create one input report per application type

It is not a good idea to try to fit all types of applications in the
same input report. There are a lot of devices that are needing
the quirk HID_MULTI_INPUT but this quirk doesn't match the actual HID
description as it is based on the report ID.

Given that most devices with MULTI_INPUT I can think of split nicely
the devices inputs into application, it is a good thing to split the
devices by default based on this assumption.

Also make hid-multitouch following this rule, to not have to deal
with too many input created.

While we are at it, fix some checkpatch complaints about converting
'unsigned' to 'unsigned int'.

Signed-off-by: Benjamin Tissoires <benjamin.tissoires@redhat.com>
Signed-off-by: Jiri Kosina <jkosina@suse.cz>

1 files changed, 3 insertions, 3 deletions

diff --git a/drivers/hid/hid-magicmouse.c b/drivers/hid/hid-magicmouse.c
index 42ed887ba0be..b454c4386157 100644
--- a/drivers/hid/hid-magicmouse.c
+++ b/drivers/hid/hid-magicmouse.c
@@ -531,12 +531,12 @@ static int magicmouse_probe(struct hid_device *hdev,
 
         if (id->product == USB_DEVICE_ID_APPLE_MAGICMOUSE)
                 report = hid_register_report(hdev, HID_INPUT_REPORT,
-                        MOUSE_REPORT_ID);
+                        MOUSE_REPORT_ID, 0);
         else { /* USB_DEVICE_ID_APPLE_MAGICTRACKPAD */
                 report = hid_register_report(hdev, HID_INPUT_REPORT,
-                        TRACKPAD_REPORT_ID);
+                        TRACKPAD_REPORT_ID, 0);
                 report = hid_register_report(hdev, HID_INPUT_REPORT,
-                        DOUBLE_REPORT_ID);
+                        DOUBLE_REPORT_ID, 0);
         }
 
         if (!report) {