1. 20 Nov, 2010 2 commits
    • Sarah Sharp's avatar
      xhci: Setup array of USB 2.0 and USB 3.0 ports. · da6699ce
      Sarah Sharp authored
      An xHCI host controller contains USB 2.0 and USB 3.0 ports, which can
      occur in any order in the PORTSC registers.  We cannot read the port speed
      bits in the PORTSC registers at init time to determine the port speed,
      since those bits are only valid when a USB device is plugged into the
      port.
      
      Instead, we read the "Supported Protocol Capability" registers in the xHC
      Extended Capabilities space.  Those describe the protocol, port offset in
      the PORTSC registers, and port count.  We use those registers to create
      two arrays of pointers to the PORTSC registers, one for USB 3.0 ports, and
      another for USB 2.0 ports.  A third array keeps track of the port protocol
      major revision, and is indexed with the internal xHCI port number.
      
      This commit is a bit big, but it should be queued for stable because the "Don't
      let the USB core disable SuperSpeed ports" patch depends on it.  There is no
      other way to determine which ports are SuperSpeed ports without this patch.
      Signed-off-by: default avatarSarah Sharp <sarah.a.sharp@linux.intel.com>
      Tested-by: default avatarDon Zickus <dzickus@redhat.com>
      Cc: stable@kernel.org
      da6699ce
    • Paul Zimmerman's avatar
      xhci: Fix reset-device and configure-endpoint commands · 7a3783ef
      Paul Zimmerman authored
      We have been having problems with the USB-IF Gold Tree tests when plugging
      and unplugging devices from the tree. I have seen that the reset-device
      and configure-endpoint commands, which are invoked from
      xhci_discover_or_reset_device() and xhci_configure_endpoint(), will sometimes
      time out.
      
      After much debugging, I determined that the commands themselves do not actually
      time out, but rather their completion events do not get delivered to the right
      place.
      
      This happens when the command ring has just wrapped around, and it's enqueue
      pointer is left pointing to the link TRB. xhci_discover_or_reset_device() and
      xhci_configure_endpoint() use the enqueue pointer directly as their command
      TRB pointer, without checking whether it's pointing to the link TRB.
      
      When the completion event arrives, if the command TRB is pointing to the link
      TRB, the check against the command ring dequeue pointer in
      handle_cmd_in_cmd_wait_list() fails, so the completion inside the command does
      not get signaled.
      
      The patch below fixes the timeout problem for me.
      
      This should be queued for the 2.6.35 and 2.6.36 stable trees.
      Signed-off-by: default avatarPaul Zimmerman <paulz@synopsys.com>
      Signed-off-by: default avatarSarah Sharp <sarah.a.sharp@linux.intel.com>
      Cc: stable@kernel.org
      7a3783ef
  2. 16 Nov, 2010 4 commits
    • Alan Stern's avatar
      USB: EHCI: fix obscure race in ehci_endpoint_disable · 02e2c51b
      Alan Stern authored
      This patch (as1435) fixes an obscure and unlikely race in ehci-hcd.
      When an async URB is unlinked, the corresponding QH is removed from
      the async list.  If the QH's endpoint is then disabled while the URB
      is being given back, ehci_endpoint_disable() won't find the QH on the
      async list, causing it to believe that the QH has been lost.  This
      will lead to a memory leak at best and quite possibly to an oops.
      
      The solution is to trust usbcore not to lose track of endpoints.  If
      the QH isn't on the async list then it doesn't need to be taken off
      the list, but the driver should still wait for the QH to become IDLE
      before disabling it.
      
      In theory this fixes Bugzilla #20182.  In fact the race is so rare
      that it's not possible to tell whether the bug is still present.
      However, adding delays and making other changes to force the race
      seems to show that the patch works.
      Signed-off-by: default avatarAlan Stern <stern@rowland.harvard.edu>
      Reported-by: default avatarStefan Richter <stefanr@s5r6.in-berlin.de>
      CC: David Brownell <david-b@pacbell.net>
      CC: stable <stable@kernel.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      02e2c51b
    • Josh Wu's avatar
      USB: gadget: AT91: fix typo in atmel_usba_udc driver · b4880951
      Josh Wu authored
      compile fix for bug introduced by 969affff)
      Signed-off-by: default avatarJosh Wu <josh.wu@atmel.com>
      Cc: Jiri Kosina <jkosina@suse.cz>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      b4880951
    • Axel Lin's avatar
      USB: isp1362-hcd - fix section mismatch warning · f52022b5
      Axel Lin authored
      Fix section mismatch warning by using "__devinit" annotation for isp1362_probe.
      
      WARNING: drivers/usb/host/isp1362-hcd.o(.data+0x0): Section mismatch in reference from the variable isp1362_driver to the function .init.text:isp1362_probe()
      The variable isp1362_driver references
      the function __init isp1362_probe()
      If the reference is valid then annotate the
      variable with __init* or __refdata (see linux/init.h) or name the variable:
      *_template, *_timer, *_sht, *_ops, *_probe, *_probe_one, *_console,
      Signed-off-by: default avatarAxel Lin <axel.lin@gmail.com>
      Acked-by: default avatarMike Frysinger <vapier@gentoo.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      f52022b5
    • Andiry Xu's avatar
      USB: EHCI: AMD periodic frame list table quirk · 3d091a6f
      Andiry Xu authored
      On AMD SB700/SB800/Hudson-2/3 platforms, USB EHCI controller may read/write
      to memory space not allocated to USB controller if there is longer than
      normal latency on DMA read encountered. In this condition the exposure will
      be encountered only if the driver has following format of Periodic Frame
      List link pointer structure:
      
      For any idle periodic schedule, the Frame List link pointers that have the
      T-bit set to 1 intending to terminate the use of frame list link pointer
      as a physical memory pointer.
      
      Idle periodic schedule Frame List Link pointer shoule be in the following
      format to avoid the issue:
      
      Frame list link pointer should be always contains a valid pointer to a
      inactive QHead with T-bit set to 0.
      Signed-off-by: default avatarAndiry Xu <andiry.xu@amd.com>
      Acked-by: default avatarDavid Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
      3d091a6f
  3. 15 Nov, 2010 10 commits
  4. 13 Nov, 2010 12 commits
  5. 12 Nov, 2010 12 commits