1. 21 2月, 2019 6 次提交
  2. 14 1月, 2019 1 次提交
  3. 17 12月, 2018 1 次提交
  4. 07 12月, 2018 1 次提交
  5. 30 11月, 2018 2 次提交
    • H
      HID: asus: Add support for the ASUS FX503VD laptop · 2340bad5
      Hans de Goede 提交于
      The ASUS FX503VD laptop uses an USB keyboard with several hotkeys
      which use the Asus Vendor specific UsagePage.
      
      This uses two usage-codes within the page which have not been seen
      before, 0x7c for its mic-mute hotkey and 0x99 for Fn+F5 which has
      a "fan" symbol as hotkey symbol on the keyb. we map this to KEY_PROG4
      (PROG1-PROG3 are already used).
      
      This commit adds the mappings for the 2 new usage codes and the USB-ids
      for this keyboard to the hid-asus driver.
      Signed-off-by: NHans de Goede <hdegoede@redhat.com>
      Signed-off-by: NBenjamin Tissoires <benjamin.tissoires@redhat.com>
      2340bad5
    • H
      HID: ite: Add USB id match for another ITE based keyboard rfkill key quirk · 40502074
      Hans de Goede 提交于
      The 258a:6a88 keyboard-dock shipped with the Prowise PT301 tablet is
      likely another ITE based design. The controller die is directly bonded
      to the PCB with a blob of black glue on top so there are no markings and
      the 258a vendor-id used is unknown anywhere. But the keyboard has the
      exact same hotkeys mapped to Fn+F1 - F10 as the other ITE8595 keyboard
      I have *and* it has the same quirky behavior wrt the rfkill hotkey.
      
      Either way as said this keyboard has the same quirk for its rfkill /
      airplane mode hotkey as the ITE 8595 chip, it only sends a single release
      event when pressed and released, it never sends a press event.
      
      This commit adds the 258a:6a88 USB id to the hid-ite id-table, fixing
      the rfkill key not working on this keyboard.
      Signed-off-by: NHans de Goede <hdegoede@redhat.com>
      Signed-off-by: NBenjamin Tissoires <benjamin.tissoires@redhat.com>
      40502074
  6. 21 11月, 2018 1 次提交
  7. 20 11月, 2018 1 次提交
  8. 19 11月, 2018 2 次提交
    • K
      HID: i2c-hid: Disable runtime PM for LG touchscreen · 86c31524
      Kai-Heng Feng 提交于
      LG touchscreen (1fd2:8001) stops working after reboot:
      [ 4.859153] i2c_hid i2c-SAPS2101:00: i2c_hid_get_input: incomplete report (64/66)
      [ 4.936070] i2c_hid i2c-SAPS2101:00: i2c_hid_get_input: incomplete report (64/66)
      [ 9.948224] i2c_hid i2c-SAPS2101:00: failed to reset device.
      
      The device in question stops working after receives SLEEP, ON, SLEEP
      commands in a short period. The scenario is like this:
      - Once the desktop session closes, it also closed the hid device, so the
      device gets runtime suspended and receives a SLEEP command.
      - Before calling shutdown callback, it gets runtime resumed and received
      an ON command.
      - In the shutdown callback, it receives another SLEEP command.
      
      I failed to find a reliable interval between ON/SLEEP commands that can
      make it work, so let's simply disable runtime PM for the device.
      Signed-off-by: NKai-Heng Feng <kai.heng.feng@canonical.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      86c31524
    • K
      HID: multitouch: Add pointstick support for Cirque Touchpad · 12d43aac
      Kai-Heng Feng 提交于
      Cirque Touchpad/Pointstick combo is similar to Alps devices, it requires
      MT_CLS_WIN_8_DUAL to expose its pointstick as a mouse.
      Signed-off-by: NKai-Heng Feng <kai.heng.feng@canonical.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      12d43aac
  9. 12 11月, 2018 1 次提交
  10. 08 11月, 2018 1 次提交
  11. 26 10月, 2018 1 次提交
  12. 12 10月, 2018 1 次提交
  13. 03 10月, 2018 1 次提交
  14. 24 9月, 2018 2 次提交
    • H
      HID: hid-bigbenff: driver for BigBen Interactive PS3OFMINIPAD gamepad · 256a90ed
      Hanno Zulla 提交于
      This is a driver to fix input mapping and add LED & force feedback
      support for the "BigBen Interactive Kid-friendly Wired Controller
      PS3OFMINIPAD SONY" gamepad with USB id 146b:0902. It was originally
      sold as a PS3 accessory and makes a very nice gamepad for Retropie.
      Signed-off-by: NHanno Zulla <kontakt@hanno.de>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      256a90ed
    • H
      HID: i2c-hid: Remove RESEND_REPORT_DESCR quirk and its handling · afbb1169
      Hans de Goede 提交于
      Commit 52cf93e6 ("HID: i2c-hid: Don't reset device upon system resume")
      removes the need for the RESEND_REPORT_DESCR quirk for Raydium devices, but
      kept it for the SIS device id 10FB touchscreens, as the author of that
      commit could not determine if the quirk is still necessary there.
      
      I've tested suspend/resume on a Toshiba Click Mini L9W-B which is the
      device for which this quirk was added in the first place and with the
      "Don't reset device upon system resume" fix the quirk is no longer
      necessary, so this commit removes it.
      
      Note even better I also had some other devices with SIS touchscreens which
      suspend/resume issues, where the RESEND_REPORT_DESCR quirk did not help.
      
      I've also tested these devices with the "Don't reset device upon system
      resume" fix and I'm happy to report that that fix also fixes touchscreen
      resume on the following devices:
      
      Asus T100HA
      Asus T200TA
      Peaq C1010
      
      Cc: Kai-Heng Feng <kai.heng.feng@canonical.com>
      Acked-by: NBenjamin Tissoires <benjamin.tissoires@redhat.com>
      Signed-off-by: NHans de Goede <hdegoede@redhat.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      afbb1169
  15. 06 9月, 2018 1 次提交
    • K
      HID: i2c-hid: Don't reset device upon system resume · 52cf93e6
      Kai-Heng Feng 提交于
      Raydium touchscreen triggers interrupt storm after system-wide suspend:
      
      	[ 179.085033] i2c_hid i2c-CUST0000:00: i2c_hid_get_input: incomplete report (58/65535)
      
      According to Raydium, Windows driver does not reset the device after system
      resume.
      
      The HID over I2C spec does specify a reset should be used at intialization, but
      it doesn't specify if reset is required for system suspend.
      
      Tested this patch on other i2c-hid touchpanels I have and those touchpanels do
      work after S3 without doing reset. If any regression happens to other
      touchpanel vendors, we can use quirk for Raydium devices.
      
      There's still one device uses I2C_HID_QUIRK_RESEND_REPORT_DESCR so keep it
      there.
      
      Cc: Aaron Ma <aaron.ma@canonical.com>
      Cc: AceLan Kao <acelan.kao@canonical.com>
      Signed-off-by: NKai-Heng Feng <kai.heng.feng@canonical.com>
      Reviewed-by: NBenjamin Tissoires <benjamin.tissoires@gmail.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      52cf93e6
  16. 05 9月, 2018 1 次提交
  17. 30 8月, 2018 1 次提交
  18. 28 8月, 2018 2 次提交
  19. 23 7月, 2018 1 次提交
  20. 17 7月, 2018 2 次提交
  21. 11 6月, 2018 1 次提交
  22. 15 5月, 2018 1 次提交
    • R
      HID: add driver for Valve Steam Controller · c164d6ab
      Rodrigo Rivas Costa 提交于
      There are two ways to connect the Steam Controller: directly to the USB
      or with the USB wireless adapter.  Both methods are similar, but the
      wireless adapter can connect up to 4 devices at the same time.
      
      The wired device will appear as 3 interfaces: a virtual mouse, a virtual
      keyboard and a custom HID device.
      
      The wireless device will appear as 5 interfaces: a virtual keyboard and
      4 custom HID devices, that will remain silent until a device is actually
      connected.
      
      The custom HID device has a report descriptor with all vendor specific
      usages, so the hid-generic is not very useful. In a PC/SteamBox Valve
      Steam Client provices a software translation by using hidraw and a
      creates a uinput virtual gamepad and XTest keyboard/mouse.
      
      This driver intercepts the hidraw usage, so it can get out of the way
      when the Steam Client is in use.
      Signed-off-by: NRodrigo Rivas Costa <rodrigorivascosta@gmail.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      c164d6ab
  23. 09 5月, 2018 1 次提交
  24. 25 4月, 2018 1 次提交
  25. 17 4月, 2018 1 次提交
  26. 12 4月, 2018 1 次提交
  27. 27 3月, 2018 1 次提交
  28. 06 3月, 2018 3 次提交
    • T
      HID: sony: Add touchpad support for NSG-MR5U and NSG-MR7U remotes · b7289cb1
      Todd Kelner 提交于
      Sony's NSG-MR5U and NSG-MR7U remote controls have a full keyboard and a
      touchpad.  The keyboard is already supported by the existing Linux
      kernel and drivers but the touchpad is not recognized.  This patch adds
      the coded needed to bring full functionality to the touchpad.
      
      Note that these remotes use the vendor code for SMK even though they are
      Sony branded.
      
      Known limitations
      - The built-in accelerometers are not supported by these changes
      - When the Drag (Fn) key is used as a mouse button, the button is
      automatically released when the key begins repeating.  There are two
        workarounds for this 1) Use the button behind the touchpad instead of
        the Drag (Fn) key or 2) Disable the key repeat functionality or
        increase the key repeat delay.
      Signed-off-by: NTodd Kelner <tsopdump@gmail.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      b7289cb1
    • T
      HID: elecom: add support for EX-G M-XT4DRBK trackball · fbb77e88
      Tomasz Kramkowski 提交于
      This patch enables the 6th button on the ELECOM EX-G M-XT4DRBK
      trackball mouse.
      
      This is a left handed EX-G variant which only comes in a wireless (D)
      model. It has a total of 6 buttons but one of these is not available
      because of how the HID descriptor is configured.
      Signed-off-by: NTomasz Kramkowski <tk@the-tk.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      fbb77e88
    • T
      HID: elecom: refer to trackballs by model name instead of series · 79837ede
      Tomasz Kramkowski 提交于
      This patch changes all references to ELECOM trackballs using their
      series name to refer to them by their model name.
      
      ELECOM provides multiple series of mice such as EX-G, HUGE, and DEFT.
      Although it has not caused conflicts in the driver, there can be more
      than one iteration of mice in each series. For example, there are 7
      variants of EX-G trackballs but only three (M-XT3URBK, M-XT3DRBK, and
      M-XT4DRBK) need a driver to work correctly.
      
      There are also 4 DEFT series trackballs but two of them have the same
      VID:PID as the other two. I picked the earlier model for the naming of
      the PID macros.
      Signed-off-by: NTomasz Kramkowski <tk@the-tk.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      79837ede