From: David Brownell <david-b@pacbell.net>
To: linux-usb-devel@lists.sourceforge.net, me@felipebalbi.com
Cc: gregkh@suse.de, Robin Getz <rgetz@blackfin.uclinux.org>,
linux-kernel@vger.kernel.org
Subject: Re: [linux-usb-devel] [PATCH] : Allow embedded developers USB options normally reserved for OTG
Date: Wed, 2 Jan 2008 11:14:10 -0800 [thread overview]
Message-ID: <200801021114.11074.david-b@pacbell.net> (raw)
In-Reply-To: <20080102185745.GA17890@kedavra.cpe.vivax.com.br>
On Wednesday 02 January 2008, Felipe Balbi wrote:
> The problem I see here is that my only
> "user" is musb driver, currently only available on linux-omap git tree.
>
> Maybe it's time to send it to mainline, what do you think Dave?
Probably time, yes. ISTR the main open issues are on host side
behavior, and it'll be easier to sort those out if musb_hdrc can
be updated without a few months intervening lag time.
Plus that'll make it easier to merge the Blackfin platform updates
for that driver. It's fine that musb_hdrc works on N800, N810,
DaVinci, OMAP2430, and more ... but non-TI chips also integrate
that high speed OTG silicon. :)
- Dave
next prev parent reply other threads:[~2008-01-02 19:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-02 14:48 [PATCH] : Allow embedded developers USB options normally reserved for OTG Robin Getz
2008-01-02 18:47 ` [linux-usb-devel] " David Brownell
2008-01-02 18:57 ` Felipe Balbi
2008-01-02 19:14 ` David Brownell [this message]
2008-01-02 18:58 ` Mike Frysinger
2008-01-02 19:16 ` David Brownell
2008-01-02 19:46 ` Alan Stern
2008-01-02 20:25 ` David Brownell
2008-01-02 20:58 ` Alan Stern
2008-01-03 3:50 ` David Brownell
2008-01-03 3:52 ` Bryan Wu
2008-01-03 17:01 ` Richard D
2008-01-03 3:03 ` Robin Getz
2008-01-03 3:43 ` David Brownell
2008-01-03 4:40 ` Bryan Wu
2008-01-03 7:36 ` David Brownell
2008-01-03 8:05 ` Bryan Wu
2008-01-03 17:04 ` Richard D
2008-01-04 1:20 ` Robin Getz
2008-01-03 7:58 ` Robin Getz
2008-01-03 3:47 ` Bryan Wu
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=200801021114.11074.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=me@felipebalbi.com \
--cc=rgetz@blackfin.uclinux.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