From: David Brownell <david-b@pacbell.net>
To: Steve Sakoman <sakoman@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: musb broken, was [RFC 0/2] McBSP and ASoC OMAP update patches for 2430 and 34xx
Date: Sat, 6 Sep 2008 22:23:10 -0700 [thread overview]
Message-ID: <200809062223.10845.david-b@pacbell.net> (raw)
In-Reply-To: <5e088bd90809061449l5b9d2d2dm1920301b70e6e5bf@mail.gmail.com>
On Saturday 06 September 2008, Steve Sakoman wrote:
> On Fri, Sep 5, 2008 at 10:52 AM, Tony Lindgren <tony@atomide.com> wrote:
> > * Steve Sakoman <sakoman@gmail.com> [080905 10:24]:
> >> > Hmm, is the musb broken now?
> >>
> >> It is on Overo if I base my patches against current top of tree
> >> (a376251519ced5831ed07ed234430725230ed93a)
> >>
> >> Doesn't crash, just quietly doesn't work. I hear from Beagle folk
> >> that musb doesn't work there either. ...
A while back I tried a patch making the rc3-omap code match mainline
(more or less) on Beagle, and it failed ... so I've been tracking
down various RC3 issues.
I don't have all of them yet, but various "used to work" (on DaVinci
and TUSB6010) scenarios -- plugging/unplugging the B side of a cable
(Beagle == host), reboot with cable connected (Beagle == peripheral)
are being trouble.
There's also a notification issue with CDC Ethernet ... if the usb0
interface (Beagle == peripheral) is brought up before the host gets
connected, the host can't talk to it. I just sent that patch in:
http://marc.info/?l=linux-usb&m=122076214105934&w=2
> Mans has a patch in his git:
>
> http://git.mansr.com/?p=linux-omap;a=commitdiff;h=1e5bc41773bb981b3a89bd762becf98c72be5e4c
>
> Neither of us understand musb details enough to propose this as *the*
> fix, but it seems likely to be the issue.
Missing that should probably make trouble, yes.
next prev parent reply other threads:[~2008-09-07 5:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-06 21:49 musb broken, was [RFC 0/2] McBSP and ASoC OMAP update patches for 2430 and 34xx Steve Sakoman
2008-09-07 5:23 ` David Brownell [this message]
2008-09-07 15:19 ` Måns Rullgård
2008-09-07 17:37 ` David Brownell
2008-09-07 18:08 ` Steve Sakoman
2008-09-07 18:17 ` Måns Rullgård
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=200809062223.10845.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--cc=sakoman@gmail.com \
--cc=tony@atomide.com \
/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