public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: david.hagood@gmail.com
To: linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Odd behavior in musb_hdrc OTG if gadget drivers are modules
Date: Thu, 22 Jan 2009 15:46:28 -0600 (CST)	[thread overview]
Message-ID: <6cc6e376b34fd371cf946c1660c97f6e.squirrel@localhost> (raw)

I've spend the day tracking down a weird behavior on a Beagleboard with
2.6.29-rc2-omap1.

If you select the mode for the musb to operate in OnTheGo mode
(CONFIG_USB_MUSB_OTG), and if you compile the gadget drivers as modules,
the the USB port will NOT be brought up at system boot, even if it has a
USB mini-A cable plugged in (and thus should be in host mode, not gadget
mode).

If you then modprobe an appropriate gadget driver, then the interface will
be brought up in host mode.

If you DON'T modprobe a gadget driver, AND you attempt to force the port
to host mode by
  echo host > /sys/devices/platform/musb_hdrc/mode

Then we get a kernel page fault trying to change modes, even though we are
changing to host mode, which should be valid.

It seems to me that either the port should be brought up in host mode if
no gadget drivers are loaded, and an attempt to switch to gadget mode
should fail if no driver is loaded, OR there should be a config options to
set what the default gadget driver is in the absence of one being loaded
by the system.



             reply	other threads:[~2009-01-22 21:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-22 21:46 david.hagood [this message]
2009-02-25 21:17 ` Odd behavior in musb_hdrc OTG if gadget drivers are modules Felipe Balbi

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=6cc6e376b34fd371cf946c1660c97f6e.squirrel@localhost \
    --to=david.hagood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox