Hi Jiri, Thanks a lot for that. My apologies. I didn't thanked Henrik and commented his review. So thank you Henrik. (the "break" here is not an optimisation as field->maxusage may be greater than the real report count). I'm currently quite overloaded with the hid over i2c bus, and I'm getting some very goods results. I'm stuck with the acpi part, but the rest of it is working pretty good for a draft. I'll keep you inform soon. Cheers, Benjamin On Thu, Jun 28, 2012 at 10:31 AM, Jiri Kosina <jkosina@xxxxxxx> wrote: > On Tue, 19 Jun 2012, benjamin.tissoires wrote: > >> From: Benjamin Tissoires <benjamin.tissoires@xxxxxxx> >> >> Zytronic panels shows a new way of setting the Input Mode feature. >> This feature is put in the second usage in the HID feature, instead >> of the first, as the majority of the multitouch devices. >> >> This patch adds a detection step when the feature is presented to know >> where the feature is located in the report. We can then trigger the right >> command to the device. This removes the magic number "0" in the function >> mt_set_input_mode. > > I have applied 1/3 and 3/3. For 2/3, Henrik raised concern which I'd like > to have resolved first. > > Thanks! > > -- > Jiri Kosina > SUSE Labs -- 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
