1. 27 10月, 2021 1 次提交
  2. 20 8月, 2021 1 次提交
  3. 28 7月, 2021 2 次提交
  4. 05 5月, 2021 2 次提交
    • M
      HID: a4tech: use A4_2WHEEL_MOUSE_HACK_B8 for A4TECH NB-95 · 9858c74c
      Mateusz Jończyk 提交于
      This mouse has a horizontal wheel that requires special handling.
      Without this patch, the horizontal wheel acts like a vertical wheel.
      
      In the output of `hidrd-convert` for this mouse, there is a
      `Usage (B8h)` field. It corresponds to a byte in packets sent by the
      device that specifies which wheel generated an input event.
      
      The name "A4TECH" is spelled in all capitals on the company website.
      Signed-off-by: NMateusz Jończyk <mat.jonczyk@o2.pl>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      9858c74c
    • B
      HID: semitek: new driver for GK6X series keyboards · 6a012686
      Benjamin Moody 提交于
      A number of USB keyboards, using the Semitek firmware, are capable of
      handling arbitrary N-key rollover, but due to a buggy report
      descriptor, keys beyond the sixth cannot be detected by the generic
      HID driver.
      
      There are numerous hardware variants sold by several vendors, mostly
      using generic names like "GK61" for the 61-key version.  These
      keyboards are sometimes known collectively as the "GK6X" series.
      
      The keyboard has three USB interfaces.  Interface 0 uses the standard
      HID boot protocol, limited to eight modifier keys and six normal keys;
      interface 2 uses a custom report format that permits any number of
      keys.  If more than six keys are pressed simultaneously, the first six
      are reported via interface 0 while subsequent keys are reported via
      interface 2.
      
      (Interface 1 uses a custom protocol for reprogramming the keyboard;
      this can be controlled through userspace tools and is not of concern
      for the present driver.)
      
      The report descriptor for interface 2, however, is incorrect (for
      report ID 0x04, the input field is marked as "array" rather than
      "variable".)  The descriptor appears to be correct in other respects,
      so we simply replace the incorrect byte before parsing the descriptor.
      Signed-off-by: NBenjamin Moody <bmoody@member.fsf.org>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      6a012686
  5. 30 3月, 2021 1 次提交
  6. 20 3月, 2021 1 次提交
  7. 19 3月, 2021 1 次提交
  8. 16 3月, 2021 1 次提交
  9. 11 2月, 2021 4 次提交
  10. 18 1月, 2021 1 次提交
  11. 04 1月, 2021 1 次提交
    • A
      HID: sony: select CONFIG_CRC32 · 273435a1
      Arnd Bergmann 提交于
      Without crc32 support, this driver fails to link:
      
      arm-linux-gnueabi-ld: drivers/hid/hid-sony.o: in function `sony_raw_event':
      hid-sony.c:(.text+0x8f4): undefined reference to `crc32_le'
      arm-linux-gnueabi-ld: hid-sony.c:(.text+0x900): undefined reference to `crc32_le'
      arm-linux-gnueabi-ld: drivers/hid/hid-sony.o:hid-sony.c:(.text+0x4408): more undefined references to `crc32_le' follow
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      273435a1
  12. 27 11月, 2020 1 次提交
  13. 22 10月, 2020 1 次提交
  14. 01 10月, 2020 1 次提交
  15. 20 7月, 2020 1 次提交
  16. 14 6月, 2020 1 次提交
    • M
      treewide: replace '---help---' in Kconfig files with 'help' · a7f7f624
      Masahiro Yamada 提交于
      Since commit 84af7a61 ("checkpatch: kconfig: prefer 'help' over
      '---help---'"), the number of '---help---' has been gradually
      decreasing, but there are still more than 2400 instances.
      
      This commit finishes the conversion. While I touched the lines,
      I also fixed the indentation.
      
      There are a variety of indentation styles found.
      
        a) 4 spaces + '---help---'
        b) 7 spaces + '---help---'
        c) 8 spaces + '---help---'
        d) 1 space + 1 tab + '---help---'
        e) 1 tab + '---help---'    (correct indentation)
        f) 1 tab + 1 space + '---help---'
        g) 1 tab + 2 spaces + '---help---'
      
      In order to convert all of them to 1 tab + 'help', I ran the
      following commend:
      
        $ find . -name 'Kconfig*' | xargs sed -i 's/^[[:space:]]*---help---/\thelp/'
      Signed-off-by: NMasahiro Yamada <masahiroy@kernel.org>
      a7f7f624
  17. 07 5月, 2020 1 次提交
  18. 30 4月, 2020 1 次提交
  19. 14 4月, 2020 1 次提交
  20. 06 4月, 2020 1 次提交
  21. 18 3月, 2020 2 次提交
    • S
      HID: Add driver fixing Glorious PC Gaming Race mouse report descriptor · 77a36a3a
      Samuel Čavoj 提交于
      The Glorious Model O mice (and also at least the Model O-, which is
      driver-wise the same mouse) have a bug in the descriptor of HID
      Report with ID 2. This report is used for Consumer Control buttons,
      which can be mapped using the provided Windows only software.
      
      Here is an excerpt from the original descriptor:
      
        INPUT(2)[INPUT]
          Field(0)
            Flags( Constant Variable Absolute )
          Field(1)
            Flags( Constant Variable Absolute )
          Field(2)
            Flags( Constant Variable Absolute )
      
      The issue is the Constant flag specified on all 3 fields, which
      causes the hid driver to ignore changes in these fields and
      essentialy causes the buttons to not work at all. The submitted driver
      patches the descriptor to end up with the following:
      
        INPUT(2)[INPUT]
          Field(0)
            Flags( Variable Relative )
          Field(1)
            Flags( Variable Relative )
          Field(2)
            Flags( Variable Relative )
      
      The Constant bit is reset and the Relative bit has been set in
      order to prevent repeat events when holding down the button.
      
      Additionally, the device name is changed from the hardware-reported
      "SINOWEALTH Wired Gaming Mouse" to "Glorious Model O" or "Glorious
      Model D".
      Signed-off-by: NSamuel Čavoj <sammko@sammserver.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      77a36a3a
    • G
      HID: fix Kconfig word ordering · ad81d1c8
      Geert Uytterhoeven 提交于
      Fix a silly word ordering typo.
      
      Fixes: 42337b9d ("HID: add driver for U2F Zero built-in LED and RNG")
      Signed-off-by: NGeert Uytterhoeven <geert+renesas@glider.be>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      ad81d1c8
  22. 10 3月, 2020 1 次提交
  23. 04 10月, 2019 1 次提交
  24. 03 9月, 2019 1 次提交
  25. 02 9月, 2019 1 次提交
  26. 21 5月, 2019 1 次提交
  27. 24 4月, 2019 1 次提交
  28. 15 4月, 2019 1 次提交
  29. 10 4月, 2019 1 次提交
  30. 03 4月, 2019 1 次提交
  31. 11 3月, 2019 1 次提交
    • A
      HID: hid-asus: select CONFIG_POWER_SUPPLY · a23eab89
      Arnd Bergmann 提交于
      The newly added power supply code fails to link when the power supply core
      code is disabled:
      
      drivers/hid/hid-asus.o: In function `asus_battery_get_property':
      hid-asus.c:(.text+0x11de): undefined reference to `power_supply_get_drvdata'
      drivers/hid/hid-asus.o: In function `asus_probe':
      hid-asus.c:(.text+0x170c): undefined reference to `devm_power_supply_register'
      hid-asus.c:(.text+0x1734): undefined reference to `power_supply_powers'
      drivers/hid/hid-asus.o: In function `asus_raw_event':
      hid-asus.c:(.text+0x1914): undefined reference to `power_supply_changed'
      
      Select the subsystem from Kconfig as we do for other hid drivers already.
      
      Fixes: 6311d329 ("HID: hid-asus: Add BT keyboard dock battery monitoring support")
      Signed-off-by: NArnd Bergmann <arnd@arndb.de>
      Signed-off-by: NBenjamin Tissoires <benjamin.tissoires@redhat.com>
      a23eab89
  32. 21 2月, 2019 1 次提交
  33. 15 1月, 2019 1 次提交
  34. 31 10月, 2018 1 次提交
    • D
      HID: asus: only support backlight when it's not driven by WMI · 3b692c55
      Daniel Drake 提交于
      The Asus GL502VSK has the same 0B05:1837 keyboard as we've seen in
      several Republic of Gamers laptops.
      
      However, in this model, the keybard backlight control exposed by hid-asus
      has no effect on the keyboard backlight. Instead, the keyboard
      backlight is correctly driven by asus-wmi.
      
      With two keyboard backlight devices available (and only the acer-wmi
      one working), GNOME is picking the wrong one to drive in the UI.
      
      Avoid this problem by not creating the backlight interface when we
      detect a WMI-driven keyboard backlight.
      
      We have also tested Asus GL702VMK which does have the hid-asus
      backlight present, and it still works fine with this patch (WMI method
      call returns UNSUPPORTED_METHOD).
      
      A direct "depends on ASUS_WMI" is intentionally avoided so that HID_ASUS
      users who have ASUS_WMI=n will not quietly lose their HID_ASUS driver on
      a kernel upgrade.
      Signed-off-by: NDaniel Drake <drake@endlessm.com>
      Reviewed-by: NBenjamin Tissoires <benjamin.tissoires@redhat.com>
      Signed-off-by: NAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      3b692c55