From: Felipe Balbi <me@felipebalbi.com>
To: Bill Gatliff <bgat@billgatliff.com>
Cc: "Gadiyar, Anand" <gadiyar@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Question on OTG transceivers
Date: Mon, 22 Mar 2010 18:45:48 +0200 [thread overview]
Message-ID: <20100322164547.GA3912@gandalf> (raw)
In-Reply-To: <4BA79588.4040409@billgatliff.com>
On Mon, Mar 22, 2010 at 11:06:32AM -0500, Bill Gatliff wrote:
> Gadiyar, Anand wrote:
> >
> > Actually, the way the ehci-omap driver is currently written, it assumes
> > the transceiver is present and available - you don't need a separate
> > driver to access it.
> >
> > For that matter, the same probably holds for the OTG driver as well - you
> > really don't need a driver for transparent transceivers like the SMSC332x.
> >
>
> But I get an OOPS and the system halts when I don't have a transceiver
> driver...
that smells like you're using the otg port.
--
balbi
next prev parent reply other threads:[~2010-03-22 16:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 21:35 Question on OTG transceivers Bill Gatliff
2010-03-18 3:28 ` Gadiyar, Anand
2010-03-22 16:06 ` Bill Gatliff
2010-03-22 16:45 ` Felipe Balbi [this message]
2010-03-26 10:45 ` Gadiyar, Anand
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=20100322164547.GA3912@gandalf \
--to=me@felipebalbi.com \
--cc=bgat@billgatliff.com \
--cc=gadiyar@ti.com \
--cc=linux-omap@vger.kernel.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