1. 04 9月, 2015 1 次提交
  2. 29 8月, 2015 3 次提交
  3. 24 8月, 2015 1 次提交
  4. 19 8月, 2015 1 次提交
    • D
      HID: usbhid: Fix the check for HID_RESET_PENDING in hid_io_error · 3af4e5a9
      Don Zickus 提交于
      It was reported that after 10-20 reboots, a usb keyboard plugged
      into a docking station would not work unless it was replugged in.
      
      Using usbmon, it turns out the interrupt URBs were streaming with
      callback errors of -71 for some reason.  The hid-core.c::hid_io_error was
      supposed to retry and then reset, but the reset wasn't really happening.
      
      The check for HID_NO_BANDWIDTH was inverted.  Fix was simple.
      
      Tested by reporter and locally by me by unplugging a keyboard halfway until I
      could recreate a stream of errors but no disconnect.
      Signed-off-by: NDon Zickus <dzickus@redhat.com>
      Cc: stable@vger.kernel.org
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      3af4e5a9
  5. 18 8月, 2015 3 次提交
  6. 12 8月, 2015 3 次提交
  7. 11 8月, 2015 2 次提交
    • J
      HID: wacom: Simplify 'wacom_pl_irq' · 025bcc15
      Jason Gerecke 提交于
      Unlike other IRQ functions, 'wacom_pl_irq' uses the second element of
      the 'tool' array to store information about its single pen. This makes
      the function more difficult to understand (since it doesn't follow the
      general pattern of other IRQ functions) and prevents the possibility of
      refactoring how pen state is stored.
      
      This patch rewrites 'wacom_pl_irq' to follow the usual IRQ conventions,
      including storing tool type in 'tool[0]' and implicitly tracking prox
      with the 'id[0]' variable.
      Signed-off-by: NJason Gerecke <jason.gerecke@wacom.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      025bcc15
    • J
      HID: wacom: Report correct device resolution when using the wireless adapater · 0be01712
      Jason Gerecke 提交于
      The 'wacom_wireless_work' function does not recalculate the tablet's
      resolution, causing the value contained in the 'features' struct to
      always be reported to userspace. This value is valid only for the pen
      interface, meaning that the value will be incorrect for the touchpad (if
      present). This in particular causes problems for libinput which relies
      on the reported resolution being correct.
      
      This patch adds the necessary calls to recalculate the resolution for
      each interface. This requires a little bit of code shuffling since both
      the 'wacom_set_default_phy' and 'wacom_calculate_res' are declared below
      their new first point of use in 'wacom_wireless_work'.
      Signed-off-by: NJason Gerecke <jason.gerecke@wacom.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      0be01712
  8. 10 8月, 2015 2 次提交
  9. 04 8月, 2015 4 次提交
  10. 31 7月, 2015 1 次提交
    • R
      HID: sony: Fix DS4 controller reporting rate issues · 824deff8
      Rostislav Pehlivanov 提交于
      This commit removes the cap on the DualShock 4 controller reporting rate when
      connected using Bluetooth. The previous value of '0xB0' capped the rate to only
      20.83 Hz which many userspace utilities mistook as a sign of a bad signal.
      Since a 'B' and an '8' can look similar it's possible that someone mistook the
      one for another.  The new value of '0x80' enables the full 1000 Hz peak
      reporting rate that the controller is capable of.
      
      Frank adds: "Back when the original code was written the purpose of that value
      was unknown and 0xB0 seemed to work so that's what ended up being used.  Now
      that we know what it actually does and that 0x80 is a better choice I support
      this patch."
      
      [jkosina@suse.com: update changelog]
      Signed-off-by: NRostislav Pehlivanov <atomnuker@gmail.com>
      Acked-by: NFrank Praznik <frank.praznik@gmail.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.com>
      824deff8
  11. 29 7月, 2015 3 次提交
  12. 28 7月, 2015 1 次提交
  13. 27 7月, 2015 1 次提交
  14. 24 7月, 2015 3 次提交
  15. 23 7月, 2015 3 次提交
  16. 17 7月, 2015 3 次提交
    • A
      HID: rmi: Set F01 interrupt enable register when not set · 9a98b338
      Andrew Duggan 提交于
      A firmware bug in some touchpads causes the F01 interrupt enable register
      to be cleared on reset. This register controls which RMI functions generate
      interrupts and when it is cleared, the touchpad stops reporting all data.
      This patch looks for the cleared F01 control register and writes the
      correct value based on interrupt mask computed while scanning the PDT.
      
      Fixes:
      https://bugs.freedesktop.org/show_bug.cgi?id=91102Signed-off-by: NAndrew Duggan <aduggan@synaptics.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.com>
      9a98b338
    • J
      HID: wacom: Set default device name to value from wacom->features · 2bdd163c
      Jason Gerecke 提交于
      Allocated input devices should not use the 'pen_name' by default since
      we do not know at that point in time if that is an appropriate choice
      of name. Instead, use the (tool-agnostic) name that is stored in the
      device's 'wacom_features' structure. This also has the nice side-effect
      of requring us to be explicit about the naming of the pen device, as
      we already are for touch and pad devices.
      Signed-off-by: NJason Gerecke <jason.gerecke@wacom.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.com>
      2bdd163c
    • J
      HID: wacom: Properly free inputs if 'wacom_allocate_inputs' fails · d9f2d203
      Jason Gerecke 提交于
      The 'wacom_allocate_inputs' function tries to allocate three input devices: one
      each for the pen, touch, and pad. The pointers that are returned by the
      'wacom_allocate_input' calls are temporarily stored to local variables where
      they are checked to ensure they're non-null before storing them in the
      'wacom_wac' structure. If an allocation fails,  the 'wacom_free_inputs'
      function is called to reclaim the memory. Unfortunately, 'wacom_free_inputs' is
      called prior to the pointers being copied, so it is not actually able to free
      anything.
      
      This patch has the calls to 'wacom_allocate_input' store the pointer directly
      in the 'wacom_wac' structure where they can be freed. Also, it replaces the
      call to 'wacom_free_inputs' with the (more general) 'wacom_clean_inputs' and
      removes the no-longer-used function.
      
      [jkosina@suse.com: modify to resolve conflict with 67e123ff ("Delete
       unnecessary checks")]
      Signed-off-by: NJason Gerecke <jason.gerecke@wacom.com>
      Signed-off-by: NJiri Kosina <jkosina@suse.com>
      d9f2d203
  17. 15 7月, 2015 1 次提交
  18. 14 7月, 2015 1 次提交
  19. 13 7月, 2015 3 次提交