public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <me@felipebalbi.com>
To: "Pandita, Vikram" <vikram.pandita@ti.com>
Cc: Kevin Hilman <khilman@mvista.com>,
	Linux omap <linux-omap@vger.kernel.org>
Subject: RE: OMAP3430: MUSB host and hot-plugging
Date: Thu, 20 Mar 2008 07:55:50 -0500	[thread overview]
Message-ID: <558bb41d9b118bdc524a148da2ab8864@felipebalbi.com> (raw)
In-Reply-To: <5DF83221BE20114E9C331F665ACBC0800477C178@dbde01.ent.ti.com>



On Thu, 20 Mar 2008 18:17:55 +0530, "Pandita, Vikram"
<vikram.pandita@ti.com> wrote:
> Felipe
> 
>>Sent: Thursday, March 20, 2008 6:09 PM
>>To: Pandita, Vikram
>>Cc: Kevin Hilman; Linux omap
>>Subject: RE: OMAP3430: MUSB host and hot-plugging
>>
>>
>>> If you can provide us the procedure to enable hot-plugging for MUSB on
>>> OMAP3430, we will look into this issue.
>>
>>As far as musb driver is concerned it should be just a mater of
>>building it with otg support. But as of now, I cannot get id
>>pin status to musb using twl4030.
>>
>>Maybe we still have some missing pieces on linux-omap, which I'm
>>researching on that.
> 
>  I meant if you could pass on how you have written the hot plugging
> function/agent for MUSB.
> I have not tried hot-plugging on omap. 

There should be no need for that.
twl4030-usb is using ulpi interface on 3430sdp, which means all interrupts
are
directed to musb using that interface, also musb switches between
host/peripheral
roles automatically as long as we get an id pin change interrupt.

Somehow this interrupt is not going to musb's driver when we're using ulpi
on 3430.

I have some other questions for you but it'll be privatly.

> 
>>
>>--
>>Best Regards,
>>
>>Felipe Balbi
>>http://felipebalbi.com
>>me@felipebalbi.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
> 
-- 
Best Regards,

Felipe Balbi
http://felipebalbi.com
me@felipebalbi.com


  reply	other threads:[~2008-03-20 12:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20 12:27 OMAP3430: MUSB host and hot-plugging Felipe Balbi
2008-03-20 12:34 ` Pandita, Vikram
2008-03-20 12:38   ` Felipe Balbi
2008-03-20 12:47     ` Pandita, Vikram
2008-03-20 12:55       ` Felipe Balbi [this message]
2008-03-20 17:11       ` Kevin Hilman
2008-03-20 18:57         ` Felipe Balbi
  -- strict thread matches above, loose matches on Subject: below --
2008-03-20  0:14 Kevin Hilman
2008-03-20 19:30 ` David Brownell
2008-03-20 20:00   ` Felipe Balbi
2008-03-20 20:25     ` David Brownell
2008-03-20 20:48       ` Felipe Balbi
2008-03-24  9:27       ` 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=558bb41d9b118bdc524a148da2ab8864@felipebalbi.com \
    --to=me@felipebalbi.com \
    --cc=khilman@mvista.com \
    --cc=linux-omap@vger.kernel.org \
    --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