public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Barada <peterb@logicpd.com>
To: "Gupta, Ajay Kumar" <ajay.gupta@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>
Subject: RE: Missing USB OTG ID interrupt../
Date: Tue, 13 Jan 2009 02:25:45 -0500	[thread overview]
Message-ID: <1231831546.14918.35.camel@blackhole> (raw)
In-Reply-To: <19F8576C6E063C45BE387C64729E739403ECF70A80@dbde02.ent.ti.com>

On Tue, 2009-01-13 at 11:14 +0530, Gupta, Ajay Kumar wrote:
> V
> 
> > -----Original Message-----
> > From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Peter
> > Barada
> > Sent: Tuesday, January 13, 2009 1:09 AM
> > To: linux-omap
> > Subject: Missing USB OTG ID interrupt../
> > 
> > On the current PM tree (2.6.28-rc8, revision 2beb9b4b) I have USB OTG
> > working - I see a device plugged in on boot, and it detaches when I pull
> > the cable, but it doesn't appear again when I reinsert the cable.
> 
> Vbus is switched-off when device is detached. Try using the patch at,
> http://marc.info/?l=linux-usb&m=122535802102316&w=2

Thank you, that works fine, great!  Now to test with suspend/resume...


> -ajay
> > 
> > Any ideas on why the device doesn't show up again?
> > 
> > --
> > Peter Barada <peterb@logicpd.com>
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
-- 
Peter Barada <peterb@logicpd.com>

      reply	other threads:[~2009-01-13  7:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12 19:39 Missing USB OTG ID interrupt../ Peter Barada
2009-01-13  5:44 ` Gupta, Ajay Kumar
2009-01-13  7:25   ` Peter Barada [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=1231831546.14918.35.camel@blackhole \
    --to=peterb@logicpd.com \
    --cc=ajay.gupta@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