All of lore.kernel.org
 help / color / mirror / Atom feed
From: Orjan Friberg <of@flatfrog.com>
To: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: USB gadget unreliable on software reboot (BeagleBoard xM)
Date: Tue, 4 Oct 2011 09:39:15 +0200	[thread overview]
Message-ID: <4E8AB823.3030705@flatfrog.com> (raw)

Hi,

On my BeagleBoard xM, configuring the MUSB controller in Linux to 
peripheral mode (i.e. not OTG mode) and using a built-in gadget driver, 
the gadget device sometimes does not appear after a software reboot.

I've seen this with both 2.6.32 and 2.6.39 (Angstrom 2008.1 and 2010.x 
distros, respectively).

Our own board exhibits the same behaviour.  However: configuring the 
MUSB controller in u-boot as a device and only booting as far as u-boot 
before a software reset, the device always appears.  To me this suggests 
a MUSB driver issue in Linux (as opposed to, say, PHY initialization).


I checked with a USB analyzer what happens on the bus: when it doesn't 
show up there is a reset on the bus when we reboot, but it doesn't 
re-enter full speed mode.  No SOFs are sent either.

I did a rudimentary check of the OTG registers in the TPS chip (over 
i2c) but saw nothing out of the ordinary.

I set musb_debug = 5 in musb_core.c, but no errors are reported.

I haven't looked at the MUSB controller registers yet; that's next.


Any ideas?


Thanks,
Orjan

-- 
Orjan Friberg
FlatFrog Laboratories AB

                 reply	other threads:[~2011-10-04  7:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E8AB823.3030705@flatfrog.com \
    --to=of@flatfrog.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.