From: sr@denx.de (Stefan Roese)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: omap2: fix musb usage for n8x0
Date: Thu, 18 Jul 2013 11:14:39 +0200 [thread overview]
Message-ID: <51E7B1FF.6000301@denx.de> (raw)
In-Reply-To: <1374000777-5626-1-git-send-email-zonque@gmail.com>
On 07/16/2013 08:52 PM, Daniel Mack wrote:
> Commit b7e2e75a8c ("usb: gadget: drop unused USB_GADGET_MUSB_HDRC")
> dropped a config symbol that was unused by the musb core, but it turns
> out that board support code had references to it.
>
> As the core now has a fall-back to host-only mode if support for
> dual-role is not compiled in, so we can just pass MUSB_OTG as
> mode from board files.
>
> Signed-off-by: Daniel Mack <zonque@gmail.com>
> Reported-and-tested-by: Aaro Koskinen <aaro.koskinen@iki.fi>
I'm testing musb as OTG on beagleboard (old one, not Beagle-xm). And
using the latest kernel.org version with this patch applied I see the
following messages while booting (repeatedly):
[ 4.998168] usb usb1: bus auto-suspend, wakeup 1
[ 5.003112] musb_bus_suspend 2457: trying to suspend as b_idle while active
[ 5.010498] usb usb1: bus suspend fail, err -16
[ 5.015289] hub 1-0:1.0: hub_resume
[ 5.019073] hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0000
[ 5.024963] hub 1-0:1.0: hub_suspend
[ 5.028778] usb usb1: bus auto-suspend, wakeup 1
...
This is without a cable connected to the OTG port.
Any ideas what might be missing here?
BTW: I enabled USB support for beagle in the dts this way:
+&usb_otg_hs {
+ interface-type = <0>;
+ usb-phy = <&usb2_phy>;
+ mode = <3>;
+ power = <50>;
+};
Thanks,
Stefan
next prev parent reply other threads:[~2013-07-18 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 18:52 [PATCH] ARM: omap2: fix musb usage for n8x0 Daniel Mack
2013-07-16 20:03 ` Felipe Balbi
2013-07-18 9:14 ` Stefan Roese [this message]
2013-07-18 9:18 ` Kishon Vijay Abraham I
2013-07-18 9:40 ` Stefan Roese
2013-07-18 12:02 ` Daniel Mack
2013-07-18 12:38 ` Stefan Roese
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=51E7B1FF.6000301@denx.de \
--to=sr@denx.de \
--cc=linux-arm-kernel@lists.infradead.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.