>> I previously used Vladimir Barinov's EHCI HCD glue patch on the >> 2.6.24.3 kernel and it worked. I'm currently using the 2.6.28.1 >> kernel and I see that the glue patch has already been incorporated >> into the mainline code. However, I'm having problems with enumerating >> USB devices I plug into the system. On a separate note, I still had >> to add the platform_device for the uhc in >> arch/arm/mach-ixp4xx/common.c, I'm not sure why this isn't already in >> there if the ehci-ixp4xx driver is >> supported: >> >> static struct resource ixp4xx_uhc_resources[] = { >> { >> .start = 0xcd000000, >> .end = 0xcdffffff, >> .flags = IORESOURCE_MEM, >> }, >> { >> .start = IRQ_IXP4XX_USB_HOST, >> .end = IRQ_IXP4XX_USB_HOST, >> .flags = IORESOURCE_IRQ, >> } >> }; >> >> static u64 ixp4xx_uhc_dmamask = 0xffffffff; static struct >> platform_device ixp4xx_uhc_device = { >> .name = "ixp4xx-ehci", >> .id = -1, >> .num_resources = 2, >> .resource = ixp4xx_uhc_resources, >> .dev = { >> //.platform_data = , >> .coherent_dma_mask = 0xffffffff, >> .dma_mask = &ixp4xx_uhc_dmamask, >> }, >> }; >> >> The problem I'm having is that the system doesn't recognize any memory >> drives I plug in and I get these messages: >> usb 1-1: new full speed USB device using ixp4xx-ehci and address 2 hub >> 1-0:1.0: unable to enumerate USB device on port 1 >> >> Here's a more detailed log with debugging turned on: >> hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002 ixp4xx-ehci >> ixp4xx-ehci: GetStatus port 1 status 40001813 POWER sig=j OC CSC >> CONNECT hub 1-0:1.0: port 1, status 0109, change 0001, 12 Mb/s hub >> 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x109 >> ixp4xx-ehci ixp4xx-ehci: GetStatus port 1 status 4000181d POWER sig=j >> OC PEC PE CONNECT usb 1-1: new full speed USB device using ixp4xx-ehci >> and address 4 ixp4xx-ehci ixp4xx-ehci: GetStatus port 1 status >> 40001813 POWER sig=j OC CSC CONNECT hub 1-0:1.0: unable to enumerate >> USB device on port 1 hub 1-0:1.0: state 7 ports 1 chg 0000 evt 0002 >> >> As I mentioned earlier, the patch I incorporated in 2.6.24.3 worked >> but the mainline driver is not working. I'm not sure if this problem >> lies in the ehci-ixp4xx driver itself or the ehci-hcd or ehci-hub driver? >> >> It would be great if anyone who has ran into this problem could give >> me a hand. Thanks. >> >> Vincent Mo >> >> >Turn on USB verbose debugging and Mass Storrage verbose debug. The USB verbose debugging option was already enabled and turning Mass Storage verbose debug on did not output any new messages. >What chip are you using? IXP43X or IXP46X? Attached is a patch i use >for IXP43X.. I'm using the IXP465 processor. ------------------------------------------------------------------- List admin: http://lists.arm.linux.org.uk/mailman/listinfo/linux-arm FAQ: http://www.arm.linux.org.uk/mailinglists/faq.php Etiquette: http://www.arm.linux.org.uk/mailinglists/etiquette.php
- References:
- ehci-ixp4xx driver issue
- From: Mo, Vincent
- Re: ehci-ixp4xx driver issue
- From: Karl Hiramoto
- ehci-ixp4xx driver issue
- Prev by Date: Re: MDOC G4 - md8832
- Next by Date: RE: ehci-ixp4xx driver issue
- Previous by thread: Re: ehci-ixp4xx driver issue
- Next by thread: RE: ehci-ixp4xx driver issue
- Index(es):