Skip to content
  1. Oct 20, 2012
  2. Oct 19, 2012
  3. Oct 18, 2012
    • Bjørn Mork's avatar
      USB: option: add more ZTE devices · 4b35f1c5
      Bjørn Mork authored
      
      
      Cc: <stable@vger.kernel.org>
      Signed-off-by: default avatarBjørn Mork <bjorn@mork.no>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      4b35f1c5
    • Bjørn Mork's avatar
      USB: option: blacklist net interface on ZTE devices · 1452df6f
      Bjørn Mork authored
      
      
      Based on information from the ZTE Windows drivers.
      
      Cc: <stable@vger.kernel.org>
      Signed-off-by: default avatarBjørn Mork <bjorn@mork.no>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      1452df6f
    • Greg Kroah-Hartman's avatar
      Merge tag 'fixes-for-v3.7-rc2' of... · 6b7ced68
      Greg Kroah-Hartman authored
      Merge tag 'fixes-for-v3.7-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb into usb-linus
      
      usb: fixes for v3.7-rc2
      
      Here's the first set of fixes for v3.7-rc cycle.
      
      DesignWare Core USB3 Driver (dwc3) got two fixes. The first one fixes a long
      standing bug which would keep endpoint with BUSY flag set forever if we cancel
      a transfer which has already been started by the controller. The second fix
      will just switch PHYs back off when DWC3 driver is removed.
      
      MUSB fixed a bug which would cause a Kernel Oops at least on AM3517 when
      removing a device. For some reason that particular device can fall into a
      situation where you have both Disconnect and Endpoint IRQs happen
      simultaneously (have both bits set in IRQ_STATUS register) and, because
      Disconnect Interrupt is handled before Endpoint Interrupts, we would try to
      transfer data over a disconnected device, thus generating a kernel oops.
      
      Renensas' USB DRD driver got two fixes which are a) fixing an off-by-one bug on
      the pipe iterator implementation and b) fixing Interrupt Status Clear procedure
      in order to properly clear a single Interrupt event without clearing (and
      masking) other events we didn't handle yet.
      6b7ced68