> I don't know the lg driver very well, but it looks like it's expecting > a single report ID (0), but the device is showing two report IDs: 1 > and 2. So, from the perspective of the driver, this is correct: it > wouldn't know how to deal with things since it is only expecting > Report ID 0. It seems like the driver needs to be updated for this > different device. Hi, The 'hid-lgff.c' driver supports lots of devices (see end of 'hid-lg.c'), and presumably these devices offer up a wide/varied range of HID descriptors. Does the recently introduced(/changed) check need to have prior knowledge of which 'Report ID's are actually used? If so, it possible that the change has broken a number of devices... I am trying to get the end user to test with an older kernel to see whether his device was always 'broken'. Thanks. Simon -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
