An error occurred fetching the project authors.
  1. 06 May, 2024 4 commits
  2. 22 Nov, 2023 2 commits
  3. 23 May, 2023 3 commits
  4. 13 Apr, 2023 1 commit
  5. 15 Feb, 2023 2 commits
  6. 02 Nov, 2022 1 commit
  7. 25 Aug, 2022 1 commit
    • Josh Kilmer's avatar
      HID: asus: ROG NKey: Ignore portion of 0x5a report · 1c0cc9d1
      Josh Kilmer authored
      On an Asus G513QY, of the 5 bytes in a 0x5a report, only the first byte
      is a meaningful keycode. The other bytes are zeroed out or hold garbage
      from the last packet sent to the keyboard.
      
      This patch fixes up the report descriptor for this event so that the
      general hid code will only process 1 byte for keycodes, avoiding
      spurious key events and unmapped Asus vendor usagepage code warnings.
      Signed-off-by: default avatarJosh Kilmer <srjek2@gmail.com>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      1c0cc9d1
  8. 02 Dec, 2021 1 commit
  9. 12 Nov, 2021 1 commit
  10. 19 Oct, 2021 1 commit
  11. 20 Aug, 2021 1 commit
  12. 15 Jul, 2021 1 commit
  13. 27 May, 2021 1 commit
    • Hans de Goede's avatar
      HID: asus: Cleanup Asus T101HA keyboard-dock handling · a94f66ae
      Hans de Goede authored
      There is no need to use a quirk and then return -ENODEV from the
      asus_probe() function to avoid that hid-asus binds to the hiddev
      for the USB-interface for the hid-multitouch touchpad.
      
      The hid-multitouch hiddev has a group of HID_GROUP_MULTITOUCH_WIN_8,
      so the same result can be achieved by making the hid_device_id entry
      for the dock in the asus_devices[] table only match on HID_GROUP_GENERIC
      instead of having it match HID_GROUP_ANY.
      Signed-off-by: default avatarHans de Goede <hdegoede@redhat.com>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      a94f66ae
  14. 05 May, 2021 2 commits
  15. 08 Mar, 2021 1 commit
  16. 29 Oct, 2020 1 commit
  17. 06 May, 2020 6 commits
  18. 13 Dec, 2019 1 commit
  19. 17 Jun, 2019 1 commit
  20. 30 May, 2019 1 commit
  21. 13 Feb, 2019 2 commits
  22. 17 Dec, 2018 1 commit
  23. 30 Nov, 2018 2 commits
  24. 06 Nov, 2018 1 commit
    • Arnd Bergmann's avatar
      HID: asus: fix build warning wiht CONFIG_ASUS_WMI disabled · 3fc202e8
      Arnd Bergmann authored
      asus_wmi_evaluate_method() is an empty dummy function when CONFIG_ASUS_WMI
      is disabled, or not reachable from a built-in device driver. This leads to
      a theoretical evaluation of an uninitialized variable that the compiler
      complains about, failing to check that the hardcoded return value makes
      this an unreachable code path:
      
      In file included from include/linux/printk.h:336,
                       from include/linux/kernel.h:14,
                       from include/linux/list.h:9,
                       from include/linux/dmi.h:5,
                       from drivers/hid/hid-asus.c:29:
      drivers/hid/hid-asus.c: In function 'asus_input_configured':
      include/linux/dynamic_debug.h:135:3: error: 'value' may be used uninitialized in this function [-Werror=maybe-uninitialized]
         __dynamic_dev_dbg(&descriptor, dev, fmt, \
         ^~~~~~~~~~~~~~~~~
      drivers/hid/hid-asus.c:359:6: note: 'value' was declared here
        u32 value;
            ^~~~~
      
      With an extra IS_ENABLED() check, the warning goes away.
      
      Fixes: 3b692c55 ("HID: asus: only support backlight when it's not driven by WMI")
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Acked-by: default avatarGeert Uytterhoeven <geert@linux-m68k.org>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      3fc202e8
  25. 31 Oct, 2018 1 commit
    • Daniel Drake's avatar
      HID: asus: only support backlight when it's not driven by WMI · 3b692c55
      Daniel Drake authored
      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: default avatarDaniel Drake <drake@endlessm.com>
      Reviewed-by: default avatarBenjamin Tissoires <benjamin.tissoires@redhat.com>
      Signed-off-by: default avatarAndy Shevchenko <andriy.shevchenko@linux.intel.com>
      3b692c55