> On Wed, Aug 27, 2008 at 9:38 AM, Felipe Balbi > <felipe.balbi@xxxxxxxxx> wrote: > > On Wed, Aug 27, 2008 at 09:26:34AM -0400, ext Ashwin Bihari wrote: > >> Greetings, > >> > >> I'm trying to test out the MUSB support on my OMAP-3530 based device > >> with the TWL4030 Phy. I'm using 2.6.22.18 and have tried to enable all > > > > I'll probably start the same discussion again, that's a rather old > > kernel. It would be nice to try out current git tree from [1] and report > > again if it works or not. > > > > I tried musb on omap2420 (with tusb), omap3430 and omap3530 (beagle > > board) and all of them are working. > > I'm working on a custom board namely the LogicPD Zoom OMAP3530 LV SOM > and we have support for our devkit in the 2.6.22.18 Kernel. Bringing > all of our changes to the latest tree would take me a bit of time and > I just want to validate the hardware to ensure that things are working > in their current state. You don't need ALL your changes. You only need to add a proper board file and enable the bare minimum set of drivers. You can re-use the beagle or SDP defconfigs and disable things. This much should not be hard to do. I think it'll be easier to forward port than to back-port, but it's your call. For starters, pull the latest linux-omap kernel and take a diff. The MUSB driver works fine on this as Felipe pointed out. Your first port of call would be the drivers/i2c/chips/twl4030-usb.c file. Find out why you don't get any interrupts from this. > > I suppose, like I did previously for the EHCI USB controller, I could > back-port the changes specific to the MUSB back from the latest Kernel > to my version. > > Could you send me your configuration for the beagle board? My hardware > configuration resembles that particular board. > > > > >> different settings related to MUSB and nothing seems to happen. The > >> TWL4030_USB driver builds and loads and claims that a cable is plugged > >> in even when nothing is plugged in. > > > > Sounds like a bug in twl4030-usb.c > > I agree.. > > > > >> The "musb_hdrc" driver loads up and registers with IRQs 92 and 93. The > >> TWL4030_USB driver registers with IRQ 373. As I plug-in and remove the > >> cable from the USB port, no interrupts are generated and the driver is > >> completely oblivious to what's happening.. > > > > Do you have id pin grounded ? Good point by Felipe. Check this. > > > >> I'm trying to configure the MUSB driver as a Host-only to start with, > >> I've also tried to set it as OTG with no change. I wouldn't suggest host mode unless you have the right connector (or manually ground the ID pin). It's easier to use peripheral-only and a standard cable. Note that in OTG mode, you'll need to load a gadget driver (g_ether, or g_zero or g_file_storage). Then connect a cable and see if twl4030 reports an interrupt. > > > > Use it as otg and put a gadget driver as well, it's better. > > > >> My current ".config" is as follows, could someone point me to any > >> configuration option or anything that I'm missing.. > > > > I'd just suggest you to use as otg and put a gadget driver. I'd suggest you put it in peripheral mode instead of host mode. OTG also is fine, but peripheral mode would be easier. > > Would use OTG Host not make things significantly easy as far as > software goes without having to determine the roles based on which end > of the USB cable is plugged in? > > > > > Which board are you using ? Is it some development board or a custom > > board ? > > > > Development boards have a defconfig that might help you. > > Unfortuatenly, this is a custom board for which we are creating the > defconfig..so isn't easy to jump to the latest Kernel and use another > defconfig.. > > ~ Ashwin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
