public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Barada <peterb@logicpd.com>
To: me@felipebalbi.com
Cc: felipe.balbi@nokia.com, "Pandita, Vikram" <vikram.pandita@ti.com>,
	"Gadiyar, Anand" <gadiyar@ti.com>,
	linux-omap <linux-omap@vger.kernel.org>
Subject: Re: Question regarding MUSB and dynamic fifo sizing
Date: Thu, 20 Aug 2009 12:29:02 -0400	[thread overview]
Message-ID: <1250785742.10817.38.camel@blitz> (raw)
In-Reply-To: <20090811211725.GE13969@gandalf>

On Wed, 2009-08-12 at 00:17 +0300, Felipe Balbi wrote:
> On Tue, Aug 11, 2009 at 05:17:56PM -0400, Peter Barada wrote:
> > On Tue, 2009-08-11 at 23:51 +0300, Felipe Balbi wrote:
> > > Hi,
> > > 
> > > On Tue, Aug 11, 2009 at 11:21:17AM -0400, Peter Barada wrote:
> > > > Unfortunately, with the patch, and:
> > > > 
> > > > 1) modprobe musb_hdrc
> > > > 2) modprobe g_ether
> > > > 3) connect micro-a cable
> > > > 4) echo 1 > /sys/devices/platform/musb_hdrc/connect
> > > > 
> > > > Nothing happens - no isr or output.
> > > 
> > > did you have anything at the other end of the micro-a cable ?
> > 
> > Not then. :)
> > 
> > I just connected my OTG adapter/thumbdrive,  in step three and nothing
> > no isr or output.
> > 
> > I know my OTG adapter (micro-a -> female A) is valid as I ohm'd out ID
> > and ground on the baseboard (with the SOM removed), and indeed ID is
> > shorted to ground with the adapter plugged in and open with it
> > removed...
> 
> Well, looks like I'll have to go back to my documentation tomorrow at
> the office and see if I can get it working on one board of mine,
> let's see what happens and if I have to patch anything and what.

Felipe,

I was wondering if you've had a look at this?

-- 
Peter Barada <peterb@logicpd.com>
Logic Product Development, Inc.

  reply	other threads:[~2009-08-20 16:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06 20:10 Question regarding MUSB and dynamic fifo sizing Peter Barada
2009-08-06 20:11 ` Gadiyar, Anand
2009-08-07 17:23   ` Peter Barada
2009-08-07 17:25     ` Pandita, Vikram
2009-08-07 17:55       ` Peter Barada
2009-08-07 19:22       ` Peter Barada
2009-08-07 20:17         ` Felipe Balbi
2009-08-08  6:43           ` Felipe Balbi
2009-08-08  7:17             ` Felipe Balbi
2009-08-10 14:33               ` Peter Barada
2009-08-10 16:16                 ` Felipe Balbi
2009-08-10 17:00                   ` Peter Barada
2009-08-10 17:02                     ` Felipe Balbi
2009-08-10 17:28                       ` Peter Barada
2009-08-10 18:48                         ` Felipe Balbi
2009-08-10 20:42                           ` Peter Barada
2009-08-11  6:33                             ` Felipe Balbi
2009-08-11 15:21                               ` Peter Barada
2009-08-11 20:51                                 ` Felipe Balbi
2009-08-11 21:17                                   ` Peter Barada
2009-08-11 21:17                                     ` Felipe Balbi
2009-08-20 16:29                                       ` Peter Barada [this message]
2009-08-08  3:04         ` Gupta, Ajay Kumar
2009-08-08  5:03           ` Pandita, Vikram

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=1250785742.10817.38.camel@blitz \
    --to=peterb@logicpd.com \
    --cc=felipe.balbi@nokia.com \
    --cc=gadiyar@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=me@felipebalbi.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