> -----Original Message----- > From: linux-omap-owner@xxxxxxxxxxxxxxx > [mailto:linux-omap-owner@xxxxxxxxxxxxxxx] On Behalf Of Le Van > Mao, Robert > Sent: Friday, February 29, 2008 10:09 PM > To: Felipe Balbi > Cc: linux-omap@xxxxxxxxxxxxxxx > Subject: RE: OMAP 3430 and ISP1504A USB support > > Hi, > > Thanks for the reply. I did exactly what you said but dmesg > didn't return any message at all. > > I did a cat on /proc/driver/musb_hdrc and I got this: > > root@OMAP3EVM driver]#cat /proc/driver/musb_hdrc > Status: MHDRC, Mode=Peripheral (Power=60, DevCtl=80) > OTG state: b_idle; inactive > Options: musb-dma, otg (peripheral+host), debug=3 [eps=16] > Peripheral address: 30 > Root port status: 00000000 > Gadget driver: (none) > > ep0 (hw0): 1buf, csr 0000 maxp 0000 > (queue empty) > As far as I can tell, you have not compiled OTG mode but you do not have a gadget driver loaded or built-in. Select one of the gadget driver options in menuconfig under "Device Drivers -> USB support -> USB Gadget Support". The simplest one would be Gadget Zero. One more thing to look out for would be "Rely on OTG Targeted Peripherals List" - CONFIG_USB_OTG_WHITELIST. You might want to disable it. Also, if you don't want to use the OTG mode at all, then you can simply configure the controller in host mode (CONFIG_USB_MUSB_HOST). The only thing wrong with your current configuration is that it is set to OTG mode without a gadget driver. Hope this helps. Regards, Anand > The interrupts 92 and 93 for musb_hdrc.0 were in /proc/interrupts. > > So, I am wondering what was missing? > > Regards, > > Robert > > -----Original Message----- > From: Felipe Balbi [mailto:me@xxxxxxxxxxxxxxx] > Sent: February 29, 2008 10:37 AM > To: Le Van Mao, Robert > Cc: linux-omap@xxxxxxxxxxxxxxx > Subject: Re: OMAP 3430 and ISP1504A USB support > > > > > On Fri, 29 Feb 2008 09:48:21 -0500, "Le Van Mao, Robert" > <RLeVanMao@xxxxxxxxxxxxxx> wrote: > > Hi all, > > > > I have an EVM board with an OMAP 3430 connected to a > ISP1504A OTG chips > > which has a mini-AB plug-in. I tried to put the 1504A into > host mode and > > would like to see the powering (and detection) of a > connected USB device. > > We check the ID line which seems to be grounded. > > > > The kernel is Linux version 2.6.22.1-omap1 ES2. I enabled the > > CONFIG_USB_MUSB_OTG option and I saw the usb0 created. However the > > transceiver was not in host mode. How could I put it into host mode? > > > > According to the specs of the ISP1504A, I have enable the ID_PULLUP > > regiser bit to logic 1. I am wondering where should I check > to see that > the > > registers are set properly with the MUSB drivers. > > > > Your help is appreciated and thanks in advance, > > compile your kernel with musb debug verbosity set to 3. > and follow these steps: > > 1. boot your board > 2. dmesg -c (it will clear log buffer) > 3. attach mini-a connector with device attached > 4. dmesg > > send us the last dmesg output > > Thanks > > > > > > > Starting kernel ... > > ... > > usbcore: registered new interface driver usbfs > > usbcore: registered new interface driver hub > > usbcore: registered new device driver usb > > musb_hdrc: version 2.2a/db-0.5.2/dbg, musb-dma, otg > (peripheral+host), > > debug=1 > > musb_platform_resume 175: > > 3430-resume()<7>HS USB OTG: revision 0x33, sysconfig > 0x2015, sysstatus > > 0x1, intrfsel 0x1, simenable 0x0 > > -----------> is_host_enabled > > -----------> is_peripheral_enabled > > musb_hdrc: USB OTG mode controller at c8800000 using DMA, IRQ 92 > > musb_init_controller 2148: OTG mode, status 0, dev80 > > ... > > usbmon: debugfs is not available > > usbcore: registered new interface driver cdc_acm > > drivers/usb/class/cdc-acm.c: v0.25:USB Abstract Control > Model driver for > > USB modems and ISDN adapters > > Initializing USB Mass Storage driver... > > usbcore: registered new interface driver usb-storage > > USB Mass Storage support registered. > > usbcore: registered new interface driver usbtest > > ether gadget: using random self ethernet address > > ether gadget: using random host ethernet address > > usb0: Ethernet Gadget, version: May Day 2005 > > usb0: using musb_hdrc, OUT ep1out IN ep1in STATUS ep2in > > usb0: MAC 86:e0:22:2e:a5:dd > > usb0: HOST MAC 1a:0a:8d:0b:76:d3 > > usb0: RNDIS ready > > usb_gadget_register_driver 1822: OTG startup... > > musb_hdrc musb_hdrc.0: MUSB HDRC host driver > > musb_hdrc musb_hdrc.0: new USB bus registered, assigned bus number 1 > > usb usb1: Product: MUSB HDRC host driver > > usb usb1: Manufacturer: Linux 2.6.22.1-omap1 musb-hcd > > usb usb1: SerialNumber: musb_hdrc.0 > > usb usb1: configuration #1 chosen from 1 choice > > hub 1-0:1.0: USB hub found > > hub 1-0:1.0: 1 port detected > > musb_context_store_and_suspend 253: > > MUSB-Context-SAVE (Off mode support) > > musb_platform_suspend 149: > > ... > > > > > > Robert Le Van Mao > > (450) 542-5984 > > fax : (450) 358-7707 > > RLeVanMao@xxxxxxxxxxxxxx > > www.rheinmetall.ca > > > > > > > > -- > > 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 > -- > Best Regards, > > Felipe Balbi > http://felipebalbi.com > me@xxxxxxxxxxxxxxx > > NryزXvؖ){nlj{f{yʇj fzwj:vwjض zZj > ��.n��������+%������w��{.n�����{�������ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
