An error occurred fetching the project authors.
  1. 15 Sep, 2017 6 commits
  2. 23 Feb, 2017 1 commit
  3. 30 Apr, 2016 3 commits
  4. 09 Dec, 2015 1 commit
  5. 23 Mar, 2015 3 commits
  6. 16 Jan, 2015 1 commit
  7. 22 May, 2014 1 commit
  8. 20 May, 2014 2 commits
  9. 05 May, 2014 1 commit
  10. 09 Apr, 2014 1 commit
  11. 07 Apr, 2014 2 commits
    • Benjamin Tissoires's avatar
      HID: core: do not scan constant input report · e24d0d39
      Benjamin Tissoires authored
      The Microsoft Surface Type/Touch Cover 2 is a fancy device which advertised
      itself as a multitouch device but with constant input reports.
      This way, hid_scan_report() gives the group MULTITOUCH to it, but
      hid-multitouch can not handle it due to the constant collection ignored
      by hid-input.
      
      To prevent such crap in the future, and while we do not fix this particular
      device, make the scan_report coherent with hid-input.c, and ignore constant
      input reports.
      
      CC: stable@vger.kernel.org # 3.12+
      Signed-off-by: default avatarBenjamin Tissoires <benjamin.tissoires@redhat.com>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      e24d0d39
    • Derya's avatar
      Revert "HID: microsoft: Add ID's for Surface Type/Touch Cover 2" · f3b0cbce
      Derya authored
      This reverts commit 117309c5.
      
      The MS Surface Pro 2 has an USB composite device with 3 interfaces
      - interface 0 - sensor hub
      - interface 1 - wacom digitizer
      - interface 2 - the keyboard cover, if one is attached
      This USB composite device changes it product id dependent on if and which
      keyboard cover is attached. Adding the covers to hid_have_special_driver
      prevents loading the right hid drivers for the other two interfaces, all 3
      get loaded with hid-microsoft. We don't even need hid-microsoft for the
      keyboards. We have to revert this to load the right hid modules for each
      interface.
      
      CC: stable@vger.kernel.org # kernel 3.14 only
      Signed-off-by: default avatarDerya <derya.kiran@yahoo.de>
      Signed-off-by: default avatarBenjamin Tissoires <benjamin.tissoires@redhat.com>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      f3b0cbce
  12. 24 Feb, 2014 1 commit
  13. 17 Feb, 2014 2 commits
  14. 15 Feb, 2014 1 commit
  15. 06 Feb, 2014 1 commit
  16. 03 Feb, 2014 1 commit
  17. 28 Jan, 2014 1 commit
  18. 16 Jan, 2014 2 commits
  19. 18 Dec, 2013 1 commit
  20. 16 Dec, 2013 1 commit
  21. 13 Dec, 2013 1 commit
  22. 02 Dec, 2013 1 commit
  23. 21 Nov, 2013 1 commit
  24. 19 Nov, 2013 1 commit
  25. 12 Nov, 2013 1 commit
  26. 11 Nov, 2013 1 commit
    • Forest Bond's avatar
      HID: don't ignore eGalax/D-Wav/EETI HIDs · 95d50b6c
      Forest Bond authored
      Certain devices with class HID, protocol None did not work with the HID
      driver at one point, and as a result were bound to usbtouchscreen
      instead as of commit 139ebe8d ("Input: usbtouchscreen - fix eGalax HID
      ignoring").  This change was prompted by the following report:
      
      https://lkml.org/lkml/2009/1/25/127
      
      Unfortunately, the device mentioned in this report is no longer
      available for testing.
      
      We've recently discovered that some devices with class HID, protocol
      None do not work with usbtouchscreen, but do work with usbhid.  Here is
      the report that made this evident:
      
      http://comments.gmane.org/gmane.linux.kernel.input/31710
      
      Driver binding for these devices has flip-flopped a few times, so both
      of the above reports were regressions.
      
      This situation would appear to leave us with no easy way to bind every
      device to the right driver.  However, in my own testing with several
      devices I have not found a device with class HID that does not work with
      the current HID driver.  It is my belief that changes to the HID driver
      since the original report have likely fixed the issue(s) that made it
      unsuitable at the time, and that we should prefer it over usbtouchscreen
      for these devices.  In particular, HID quirks affecting these devices
      were added/removed in the following commits since then:
      
      fe6065dc HID: add multi-input quirk for eGalax Touchcontroller
      77933c35 Merge branch 'egalax' into for-linus
      ebd11fec HID: Add quirk for eGalax touch controler.
      d34c4aa4 HID: add no-get quirk for eGalax touch controller
      
      This patch makes the HID driver no longer ignore eGalax/D-Wav/EETI
      devices with class HID.  If there are in fact devices with class HID
      that still do not work with the HID driver, we will see another round of
      regressions.  In that case I propose we investigate why the device is
      not working with the HID driver rather than re-introduce regressions for
      functioning HID devices by again binding them to usbtouchscreen.
      
      The corresponding change to usbtouchscreen will be made separately.
      Signed-off-by: default avatarForest Bond <forest.bond@rapidrollout.com>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      95d50b6c
  27. 08 Nov, 2013 1 commit