* hub 2-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
@ 2009-11-20 21:25 Michael Trimarchi
2009-11-20 22:11 ` Michael Trimarchi
0 siblings, 1 reply; 2+ messages in thread
From: Michael Trimarchi @ 2009-11-20 21:25 UTC (permalink / raw)
To: linux-omap
Hi all,
I'm working on a overo board + a palo43 daughter board. I connect a camera to hit with the following result:
hub 2-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
usb 2-2: USB disconnect, address 16
gspca: disconnect complete
usb 2-2: new high speed USB device using ehci-omap and address 16
usb 2-2: New USB device found, idVendor=05a9, idProduct=a538
usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 2-2: Product: OV538 USB camera-013008-1
usb 2-2: Manufacturer: OmniVision Application Team
usb 2-2: configuration #1 chosen from 1 choice
gspca: probing 05a9:a538
ov538: sensor is ov7691
gspca: probe ok
every time...
This sometimes happen and simetimes in some boot is ok. But when I start some transaction
I have similar problem write packet on the usb device. Can you have any idea?
Michael
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: hub 2-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
2009-11-20 21:25 hub 2-0:1.0: port 2 disabled by hub (EMI?), re-enabling Michael Trimarchi
@ 2009-11-20 22:11 ` Michael Trimarchi
0 siblings, 0 replies; 2+ messages in thread
From: Michael Trimarchi @ 2009-11-20 22:11 UTC (permalink / raw)
To: linux-omap
Michael Trimarchi wrote:
> Hi all,
>
> I'm working on a overo board + a palo43 daughter board. I connect a
> camera to hit with the following result:
>
> hub 2-0:1.0: port 2 disabled by hub (EMI?),
> re-enabling... usb 2-2: USB disconnect, address
> 16 gspca: disconnect
> complete usb 2-2: new high speed USB device using ehci-omap and address
> 16 usb 2-2: New USB device found, idVendor=05a9,
> idProduct=a538 usb 2-2: New USB device strings:
> Mfr=1, Product=2, SerialNumber=0 usb 2-2: Product: OV538
> USB camera-013008-1 usb 2-2:
> Manufacturer: OmniVision Application Team
> usb 2-2: configuration #1 chosen from 1
> choice gspca: probing
> 05a9:a538 ov538:
> sensor is ov7691
> gspca: probe ok
> every time...
> This sometimes happen and simetimes in some boot is ok. But when I start
> some transaction
> I have similar problem write packet on the usb device. Can you have any
> idea?
Ok I use isoc transfer to the sensor and I use a 2.6.29 kernel openembedded tree.
# CONFIG_USB_C67X00_HCD is not set
CONFIG_USB_EHCI_HCD=y
CONFIG_OMAP_EHCI_PHY_MODE=y
# CONFIG_OMAP_EHCI_TLL_MODE is not set
CONFIG_USB_EHCI_ROOT_HUB_TT=y
Is there a part of the support patched where I can check?
Michael
>
> Michael
> --
> 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
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-11-20 22:11 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-11-20 21:25 hub 2-0:1.0: port 2 disabled by hub (EMI?), re-enabling Michael Trimarchi
2009-11-20 22:11 ` Michael Trimarchi
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.