public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <me@felipebalbi.com>
To: David Brownell <david-b@pacbell.net>
Cc: me@felipebalbi.com, "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 21:43:34 +0200	[thread overview]
Message-ID: <20081128194334.GF6525@frodo> (raw)
In-Reply-To: <200811281037.48654.david-b@pacbell.net>

On Fri, Nov 28, 2008 at 10:37:47AM -0800, David Brownell wrote:
> On Friday 28 November 2008, Felipe Balbi wrote:
> > 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. 
> 
> It does have an I2C interface; I looked before making
> that particular comment ...

so it's better than isp1704. It's horrible only been able to talk to the
device via ulpi.

-- 
balbi

      reply	other threads:[~2008-11-28 19:43 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
2008-11-28 18:37         ` David Brownell
2008-11-28 19:43           ` Felipe Balbi [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=20081128194334.GF6525@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