From: David Brownell <david-b@pacbell.net>
To: "Pandita, Vikram" <vikram.pandita@ti.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH] MUSB HSET driver
Date: Wed, 23 May 2007 02:34:37 -0700 [thread overview]
Message-ID: <200705230234.37346.david-b@pacbell.net> (raw)
In-Reply-To: <5DF83221BE20114E9C331F665ACBC0800305CC48@dbde01.ent.ti.com>
On Wednesday 23 May 2007, Pandita, Vikram wrote:
> Hi Tony
> As per Greg's suggestion of introducing HSET driver in ope
> n source, can we push the HSET driver into MUSB for now till
> a complete implementation is made available in open source?
Please, no.
This doesn't need to be musb-specific, and if it gets merged
it'll just create more pain to rip it out when musb_hdrc goes
upstream.
A much cleaner approach is to just do this in userspace with
usbfs ... issuing control requests to the hub ports. That
will work with *ANY* high speed controller.
If the existing test mode support in the musb root hub is not
enough, just fix that bug.
- Dave
next prev parent reply other threads:[~2007-05-23 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 9:09 [PATCH] MUSB HSET driver Pandita, Vikram
2007-05-23 9:34 ` David Brownell [this message]
2007-05-23 9:44 ` Pandita, Vikram
2007-05-23 10:02 ` David Brownell
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=200705230234.37346.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-omap-open-source@linux.omap.com \
--cc=vikram.pandita@ti.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