linaro-release team mailing list archive

Thread
Date

[Bug 747639] Re: No USB devices on omap3 (beagle/overo) with recent linaro-2.6.38 based kernels or 2.6.29-rc1

To: linaro-release@xxxxxxxxxxxxxxxxxxx
From: Launchpad Bug Tracker <747639@xxxxxxxxxxxxxxxxxx>
Date: Fri, 15 Apr 2011 11:38:02 -0000
Reply-to: Bug 747639 <747639@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

This bug was fixed in the package linux-linaro-omap - 2.6.38-1002.3

---------------
linux-linaro-omap (2.6.38-1002.3) natty; urgency=low

  [ Upstream Fixes ]

  * MUSB: shutdown: Make sure block is awake before doing shutdown
    - LP: #745737
  * Fixed gpio polarity of gpio USB-phy reset.
    - LP: #747639

  [ Andy Green ]

  * LINARO: SAUCE: disable CONFIG_OMAP_RESET_CLOCKS
    - LP: #752900

  [ John Rigby ]

  * Rebase to new upstreams:
    Linux v2.6.38.1
    linaro-linux-2.6.38-upstream-29Mar2011
    Ubuntu-2.6.38-7.35
  * SAUCE: OMAP4: clock: wait for module to become accessible on
    a clk enable
    - LP: #745737
  * Rebase to new upstreams:
    Linux v2.6.38.2
    linaro-linux-2.6.38-upstream-5Apr2011
    Ubuntu-2.6.38-8.41
    - LP: #732842
  * Update configs for device tree, dvfs and lttng
  * LINARO: add building of dtb's
  * LINARO: SAUCE: Disable lowest operating freqs on omap34xx
    - LP: #732912
 -- John Rigby <john.rigby@xxxxxxxxxx>   Thu, 14 Apr 2011 12:16:06 -0600

** Changed in: linux-linaro-omap (Ubuntu)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Linaro
Release Team, which is a direct subscriber.
https://bugs.launchpad.net/bugs/747639

Title:
  No USB devices on omap3 (beagle/overo) with recent linaro-2.6.38 based
  kernels or 2.6.29-rc1

Status in Linaro Linux:
  Confirmed
Status in “linux-linaro-omap” package in Ubuntu:
  Fix Released

Bug description:
  I've been seeing USB issues on my beagle xm board with the latest
  linaro-2.6.38 tree, where when the system boots, lsusb will only show
  the root hubs, but no devices.

  
  Andy reported seeing similar on his overo board, so I bisected the issue
  down to:

  9e64bb1e9f0613093b3e34ac5402fcfef0dcc35a is the first bad commit
  commit 9e64bb1e9f0613093b3e34ac5402fcfef0dcc35a
  Author: Keshava Munegowda <keshava_mgowda@xxxxxx>
  Date:   Tue Mar 1 20:08:19 2011 +0530

      arm: omap: usb: Invoke usbhs core device initialization

      The usbhs intialization is invoked by all omap3 and omap4
      variant board files.

      Signed-off-by: Keshava Munegowda <keshava_mgowda@xxxxxx>
      Signed-off-by: Felipe Balbi <balbi@xxxxxx>

  
  I've also verified the same issue is present in 2.6.39-rc1