Re: MUSB: Idea: board-specific OTG ID pin interrupt support

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




--- On Wed, 6/2/10, Jon Povey <Jon.Povey@xxxxxxxxxxxxxxx> wrote:

> From: Jon Povey <Jon.Povey@xxxxxxxxxxxxxxx>
> Subject: MUSB: Idea: board-specific OTG ID pin interrupt support
> To: "linux-usb@xxxxxxxxxxxxxxx" <linux-usb@xxxxxxxxxxxxxxx>, "davinci-linux-open-source@xxxxxxxxxxxxxxxxxxxx" <davinci-linux-open-source@xxxxxxxxxxxxxxxxxxxx>
> Cc: "felipe.balbi@xxxxxxxxx" <felipe.balbi@xxxxxxxxx>, "Sergei Shtylyov" <sshtylyov@xxxxxxxxxx>
> Date: Wednesday, June 2, 2010, 5:52 PM
> Playing around with MUSB OTG on TI
> DM355 I am having some trouble getting A-B role switching
> working.
> 
> On my board by happy design foresight, USB ID is also wired
> to a GPIO. I am currently having a go at hacking an ID
> interrupt into the MUSB driver to prod the state machine.


I don't recall having difficulties getting the
ID-based role switching to behave with
the DM355 EVM...

  GPIO IRQs should not be needed.

Of course, maybe my memory has faded; this is
the type of situation where Mentor's silicon
design team gratuitiously disregarded OTG specs.
In fact ISTR some chicken/egg issues specifically
regarding the ID pin status bit in whichever
register held it... making host vs perhipheral
initialization a real PITA.  Maybe ULPI hooks
would help.

Regardless, I did see the cable based role
switch logic working without such gpio logic.


- Dave


--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux