1. 22 Dec, 2013 1 commit
  2. 21 Dec, 2013 1 commit
    • Greg Kroah-Hartman's avatar
      Merge tag 'for-usb-next-2013-12-20' of... · e2a3a648
      Greg Kroah-Hartman authored
      Merge tag 'for-usb-next-2013-12-20' of git://git.kernel.org/pub/scm/linux/kernel/git/sarah/xhci into usb-next
      
      Sarah writes:
      
      xhci: Cleanups, non-urgent fixes for 3.14.
      
      Happy Holidays, Greg!
      
      Here's four patches to be queued to usb-next for 3.14.
      
      One adds a module parameter to the xHCI driver to allow users to enable
      xHCI quirks without recompiling their kernel, which you've already said
      is fine.  The second patch is a bug fix for new usbtest code that's only
      in usb-next.  The third patch is simple cleanup.
      
      The last patch is a non-urgent bug fix for xHCI platform devices.  The
      bug has been in the code since 3.9.  You've been asking me to hold off
      on non-urgent bug fixes after -rc4/-rc5, so it can go into usb-next, and
      be backported to stable once 3.14 is out.
      
      These have all been tested over the past week.  I did run across one
      oops, but it turned out to be a bug in 3.12, and therefore not related
      to any of these patches.
      
      Please queue these for usb-next and 3.14.
      
      Thanks,
      Sarah Sharp
      e2a3a648
  3. 20 Dec, 2013 7 commits
  4. 19 Dec, 2013 28 commits
  5. 18 Dec, 2013 1 commit
  6. 17 Dec, 2013 2 commits
    • Lin Wang's avatar
      xhci: Remove unused variable 'addr' in inc_deq() and inc_enq(). · 599459d8
      Lin Wang authored
      This patch remove unused variable 'addr' in inc_deq() and inc_enq().
      Signed-off-by: default avatarLin Wang <lin.x.wang@intel.com>
      Signed-off-by: default avatarSarah Sharp <sarah.a.sharp@linux.intel.com>
      599459d8
    • Sarah Sharp's avatar
      usbtest: Fix BOS control test for USB 2.01 devices. · 8cf43285
      Sarah Sharp authored
      Commit c952a8ba "usb: usbtest: add a
      test case to support bos for queue control" will cause USB 2.01 and USB
      2.10 devices with a BOS descriptor to fail case 15 of the control test.
      
      The Link PM errata (released in 2007, updated in 2011) says:
      
      "The value of the bcdUSB field in the standard USB 2.0 Device Descriptor
      is used to indicate that the device supports the request to read the BOS
      Descriptor (i.e.  GetDescriptor(BOS)). Devices that support the BOS
      descriptor must have a bcdUSB value of 0201H or larger."
      
      The current code says that non-SuperSpeed devices *must* return -EPIPE,
      as this comment shows:
      
                      /* sign of this variable means:
                       *  -: tested code must return this (negative) error code
                       *  +: tested code may return this (negative too) error code
                       */
                      int                     expected = 0;
      
      This means the test will fail with USB 2.01 and USB 2.10 devices that
      provide a BOS descriptor.  Change it to only require a stall response if
      the USB device bcdUSB is less than 2.01.
      Signed-off-by: default avatarSarah Sharp <sarah.a.sharp@linux.intel.com>
      Acked-by: default avatarHuang Rui <ray.huang@amd.com>
      8cf43285