1. 11 8月, 2010 4 次提交
  2. 05 6月, 2010 1 次提交
  3. 21 5月, 2010 1 次提交
  4. 23 4月, 2010 1 次提交
  5. 30 3月, 2010 1 次提交
    • T
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo 提交于
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Guess-its-ok-by: NChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  6. 19 3月, 2010 1 次提交
  7. 16 2月, 2010 1 次提交
  8. 21 1月, 2010 1 次提交
    • A
      USB: add missing delay during remote wakeup · 49d0f078
      Alan Stern 提交于
      This patch (as1330) fixes a bug in khbud's handling of remote
      wakeups.  When a device sends a remote-wakeup request, the parent hub
      (or the host controller driver, for directly attached devices) begins
      the resume sequence and notifies khubd when the sequence finishes.  At
      this point the port's SUSPEND feature is automatically turned off.
      
      However the device needs an additional 10-ms resume-recovery time
      (TRSMRCY in the USB spec).  Khubd does not wait for this delay if the
      SUSPEND feature is off, and as a result some devices fail to behave
      properly following a remote wakeup.  This patch adds the missing
      delay to the remote-wakeup path.
      
      It also extends the resume-signalling delay used by ehci-hcd and
      uhci-hcd from 20 ms (the value in the spec) to 25 ms (the value we use
      for non-remote-wakeup resumes).  The extra time appears to help some
      devices.
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      Cc: stable <stable@kernel.org>
      Cc: Rickard Bellini <rickard.bellini@ericsson.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      
      49d0f078
  9. 12 12月, 2009 5 次提交
    • A
      USB: EHCI: add native scatter-gather support · 40f8db8f
      Alan Stern 提交于
      This patch (as1300) adds native scatter-gather support to ehci-hcd.
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      40f8db8f
    • D
      USB: Add EHCI support for MX27 and MX31 based boards · 7e8d5cd9
      Daniel Mack 提交于
      The Freescale MX27 and MX31 SoCs have a EHCI controller onboard.
      The controller is capable of USB on the go. This patch adds
      a driver to support all three of them.
      
      Users have to pass details about serial interface configuration in the
      platform data.
      
      The USB OTG core used here is the ARC core, so the driver should
      be renamed and probably be merged with ehci-fsl.c eventually.
      Signed-off-by: NSascha Hauer <s.hauer@pengutronix.de>
      Signed-off-by: NDaniel Mack <daniel@caiaq.de>
      Cc: David Brownell <dbrownell@users.sourceforge.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      7e8d5cd9
    • S
      USB: ehci: Respect IST when scheduling new split iTDs. · dccd574c
      Sarah Sharp 提交于
      The EHCI specification says that an EHCI host controller may cache part of
      the isochronous schedule.  The EHCI controller must advertise how much it
      caches in the schedule through the HCCPARAMS register isochronous
      scheduling threshold (IST) bits.
      
      In theory, adding new iTDs within the IST should be harmless.  The HW will
      follow the old cached linked list and miss the new iTD.  SW will notice HW
      missed the iTD and return 0 for the transfer length.
      
      However, Intel ICH9 chipsets (and some later chipsets) have issues when SW
      attempts to schedule a split transaction within the IST.  All transfers
      will cease being sent out that port, and the drivers will see isochronous
      packets complete with a length of zero.  Start of frames may or may not
      also disappear, causing the device to go into auto-suspend.  This "bus
      stall" will continue until a control or bulk transfer is queued to a
      device under that roothub.
      
      Most drivers will never cause this behavior, because they use multiple
      URBs with multiple packets to keep the bus busy.  If you limit the number
      of URBs to one, you may be able to hit this bug.
      
      Make sure the EHCI driver does not schedule full-speed transfers within
      the IST under an Intel chipset.  Make sure that when we fall behind the
      current microframe plus IST, we schedule the new transfer at the next
      periodic interval after the IST.
      
      Don't change the scheduling for new transfers, since the schedule slop will
      always be greater than the IST.  Allow high speed isochronous transfers to
      be scheduled within the IST, since this doesn't trigger the Intel chipset
      bug.
      
      Make sure that if the host caches the full frame, the EHCI driver's
      internal isochronous threshold (ehci->i_thresh) is set to
      8 microframes + 2 microframes wiggle room.  This is similar to what is done in
      the case where the host caches less than the full frame.
      Signed-off-by: NSarah Sharp <sarah.a.sharp@linux.intel.com>
      Cc: Alan Stern <stern@rowland.harvard.edu>
      Cc: David Brownell <dbrownell@users.sourceforge.net>
      Cc: Clemens Ladisch <clemens@ladisch.de>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      dccd574c
    • F
      USB: host: ehci: introduce omap ehci-hcd driver · 54ab2b02
      Felipe Balbi 提交于
      this driver has been sitting in linux-omap tree for quite
      some time. It adds support for omap's ehci controller.
      Signed-off-by: NFelipe Balbi <felipe.balbi@nokia.com>
      Signed-off-by: NVikram Pandita <vikram.pandita@ti.com>
      Signed-off-by: NAjay Kumar Gupta <ajay.gupta@ti.com>
      Signed-off-by: NAnand Gadiyar <gadiyar@ti.com>
      Cc: David Brownell <dbrownell@users.sourceforge.net>
      Cc: Alan Stern <stern@rowland.harvard.edu>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      54ab2b02
    • J
      USB: Add support for Xilinx USB host controller · 08d3c18e
      Julie Zhu 提交于
      Add bus glue driver for Xilinx USB host controller. The controller can be
      configured as HS only or HS/FS hybrid. The driver uses the device tree file
      to configure the driver according to the setting in the hardware system.
      
      This driver has been tested with usbtest using the NET2280 PCI card.
      Signed-off-by: NJulie Zhu <julie.zhu@xilinx.com>
      Signed-off-by: NJohn Linn <john.linn@xilinx.com>
      Acked-by: NGrant Likely <grant.likely@secretlab.ca>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      
      08d3c18e
  10. 04 12月, 2009 1 次提交
  11. 01 12月, 2009 1 次提交
  12. 23 9月, 2009 9 次提交
  13. 08 8月, 2009 1 次提交
    • A
      USB: EHCI: fix two new bugs related to Clear-TT-Buffer · 7a0f0d95
      Alan Stern 提交于
      This patch (as1273) fixes two(!) bugs introduced by the new
      Clear-TT-Buffer implementation in ehci-hcd.
      
      	It is now possible for an idle QH to have some URBs on its
      	queue -- this will happen if a Clear-TT-Buffer is pending for
      	the QH's endpoint.  Consequently we should not issue a warning
      	when someone tries to unlink an URB from an idle QH; instead
      	we should process the request immediately.
      
      	The refcounts for QHs could get messed up, because
      	submit_async() would increment the refcount when calling
      	qh_link_async() and qh_link_async() would then refuse to link
      	the QH into the schedule if a Clear-TT-Buffer was pending.
      	Instead we should increment the refcount only when the QH
      	actually is added to the schedule.  The current code tries to
      	be clever by leaving the refcount alone if an unlink is
      	immediately followed by a relink; the patch changes this to an
      	unconditional decrement and increment (although they occur in
      	the opposite order).
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      CC: David Brownell <david-b@pacbell.net>
      Tested-by: NManuel Lauss <manuel.lauss@gmail.com>
      Tested-by: NMatthijs Kooijman <matthijs@stdin.nl>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      
      
      7a0f0d95
  14. 13 7月, 2009 2 次提交
    • A
      USB: EHCI: use the new clear_tt_buffer interface · 914b7012
      Alan Stern 提交于
      This patch (as1256) changes ehci-hcd and all the other drivers in the
      EHCI family to make use of the new clear_tt_buffer callbacks.  When a
      Clear-TT-Buffer request is in progress for a QH, the QH is not allowed
      to be linked into the async schedule until the request is finished.
      At that time, if there are any URBs queued for the QH, it is linked
      into the async schedule.
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      Cc: stable <stable@kernel.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      914b7012
    • A
      USB: EHCI: update toggle state for linked QHs · a455212d
      Alan Stern 提交于
      This is an update to the "usb-ehci-update-toggle-state-for-linked-qhs"
      patch.  Since an HCD's endpoint_reset method can be called in
      interrupt context, it mustn't assume that interrupts are enabled or
      that it can sleep.
      
      So we revert to the original way of refreshing QHs' toggle bits.  Now
      the endpoint_reset method merely clears the toggle flag in the device
      structure (as was done before) and starts an async QH unlink.  When the
      QH is linked again, after the unlink finishes and an URB is queued,
      the qh_refresh() routine will update the QH's toggle bit.
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      Tested-by: NDavid <david@unsolicited.net>
      CC: David Brownell <david-b@pacbell.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      
      a455212d
  15. 16 6月, 2009 2 次提交
    • A
      USB: EHCI: update toggle state for linked QHs · b18ffd49
      Alan Stern 提交于
      This patch (as1245) fixes a bug in ehci-hcd.  When an URB is queued
      for an endpoint whose QH is already in the LINKED state, the QH
      doesn't get refreshed.  As a result, if usb_clear_halt() was called
      during the time that the QH was linked but idle, the data toggle value
      in the QH doesn't get reset.
      
      The symptom is that after a clear_halt, data gets lost and transfers
      time out.  This problem is starting to show up now because the
      "ehci-hcd unlink speedups" patch causes QHs with no queued URBs to
      remain linked for a suitable time.
      
      The patch utilizes the new endpoint_reset mechanism to fix the
      problem.  When an endpoint is reset, the new method forcibly unlinks
      the QH (if necessary) and safely updates the toggle value.  This
      allows qh_update() to be simplified and avoids using usb_device's
      toggle bits in a rather unintuitive way.
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      CC: David Brownell <david-b@pacbell.net>
      Tested-by: NDavid <david@unsolicited.net>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      b18ffd49
    • G
      USB: EHCI: use the new usb debugfs directory · 08f4e586
      Greg Kroah-Hartman 提交于
      All usb debugfs files should be behind the usb directory, not at the
      root of debugfs.
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      08f4e586
  16. 07 4月, 2009 1 次提交
  17. 25 3月, 2009 1 次提交
  18. 28 2月, 2009 1 次提交
  19. 14 11月, 2008 1 次提交
    • A
      USB: EHCI: fix handling of dead controllers · 67b2e029
      Alan Stern 提交于
      This patch (as1165) makes a few small changes in the logic used by
      ehci-hcd when it encounters a controller error:
      
      	Instead of printing out the masked status, it prints the
      	original status as read directly from the hardware.
      
      	It doesn't check for the STS_HALT status bit before taking
      	action.  The mere fact that the STS_FATAL bit is set means
      	that something bad has happened and the controller needs to
      	be reset.  With the old code this test could never succeed
      	because the STS_HALT bit was masked out from the status.
      
      I anticipate that this will prevent the occasional "irq X: nobody cared"
      problem people encounter when their EHCI controllers die.
      Signed-off-by: NAlan Stern <stern@rowland.harvard.edu>
      Cc: David Brownell <david-b@pacbell.net>
      Cc: stable <stable@kernel.org>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@suse.de>
      67b2e029
  20. 21 10月, 2008 1 次提交
  21. 18 10月, 2008 3 次提交