From: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
To: bryan.wu-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org,
Brad Parker <brad-k3bCrp9g88tBDgjK7y7TUQ@public.gmane.org>
Cc: felipe.balbi-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org,
linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kernel-team-nLRlyDuq1AZFpShjVBNYrg@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
ricardo.salveti-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] musb: move usb_add_hcd to the core init code from gadget code (v2)
Date: Mon, 10 Jan 2011 04:38:47 -0800 (PST) [thread overview]
Message-ID: <898333.24180.qm@web180304.mail.gq1.yahoo.com> (raw)
In-Reply-To: <4D2AF1EE.8010105-k3bCrp9g88tBDgjK7y7TUQ@public.gmane.org>
> With this patch, host mode works.
What about OTG and gadget modes?
The MUSB hardware is flakey with respect to
those init issues. Re-ordering host vs gadget
init has been a good way to waste a few months,
for anyone who has a few to waste. (And a
better way to waste them for folk who do NOT
but just need to stay on schedule.) One learns
quickly that the Mentor IP follows some other
state machine than the USB-OTG says, but even their
docs don't help uncover whatever init model they
are trying to follow.
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-01-10 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1279895783-7313-1-git-send-email-bryan.wu@canonical.com>
2010-08-09 13:24 ` [PATCH] musb: move usb_add_hcd to the core init code from gadget code (v2) Bryan Wu
2011-01-10 11:47 ` Brad Parker
2011-01-10 11:57 ` Felipe Balbi
2011-01-10 14:08 ` UNS: " Brad Parker
[not found] ` <4D2AF1EE.8010105-k3bCrp9g88tBDgjK7y7TUQ@public.gmane.org>
2011-01-10 12:38 ` David Brownell [this message]
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=898333.24180.qm@web180304.mail.gq1.yahoo.com \
--to=david-b-ybekhbn/0ldr7s880joybq@public.gmane.org \
--cc=brad-k3bCrp9g88tBDgjK7y7TUQ@public.gmane.org \
--cc=bryan.wu-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=felipe.balbi-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org \
--cc=kernel-team-nLRlyDuq1AZFpShjVBNYrg@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=ricardo.salveti-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.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