From: Felipe Balbi <me@felipebalbi.com>
To: David Brownell <david-b@pacbell.net>
Cc: "Gupta, Ajay Kumar" <ajay.gupta@ti.com>,
"Pillai, Manikandan" <mani.pillai@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 3/3] musb: Remvoing twl4030 dependency for OMAP3EVM MUSB
Date: Fri, 28 Nov 2008 19:59:02 +0200 [thread overview]
Message-ID: <20081128175902.GD6525@frodo> (raw)
In-Reply-To: <200811280925.26736.david-b@pacbell.net>
On Fri, Nov 28, 2008 at 09:25:26AM -0800, David Brownell wrote:
> So the answer for you is obviously to have something
> other than the musb driver hold your otg_transceiver
> driver. Like ... an isp1504.c I2C driver, which will
> eventually move to drivers/usb/otg and which calls
> the otg_set_transceiver() utility.
There's one problem here. If this is similar to isp1704, it doesn't have
a control interface. And the only way to talk to the transceiver is via
ULPI. I have patches that add musb_ulpi_read/write functions using the
musb ulpi wrapper. BUT, isp1x04 is pretty much autonomous, there isn't
much you can/have to do, the problem with them is that they don't have
an interrupt line with omap (afaict) so it's difficult to be sure when
we have to e.g. switch to host mode unless we keep polling the INT_STS
register for changes. That's too bad.
But other than that, I agree with you completely. I won't queue up
patches adding such kind of ifdefs.
--
balbi
next prev parent reply other threads:[~2008-11-28 17:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 5:28 [PATCH 3/3] musb: Remvoing twl4030 dependency for OMAP3EVM MUSB Manikandan Pillai
2008-11-28 6:46 ` Felipe Balbi
2008-11-28 6:51 ` Gupta, Ajay Kumar
2008-11-28 7:08 ` Felipe Balbi
2008-11-28 7:02 ` David Brownell
2008-11-28 7:58 ` Gupta, Ajay Kumar
2008-11-28 17:25 ` David Brownell
2008-11-28 17:59 ` Felipe Balbi [this message]
2008-11-28 18:37 ` David Brownell
2008-11-28 19:43 ` Felipe Balbi
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=20081128175902.GD6525@frodo \
--to=me@felipebalbi.com \
--cc=ajay.gupta@ti.com \
--cc=david-b@pacbell.net \
--cc=linux-omap@vger.kernel.org \
--cc=mani.pillai@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