Hi Alan,

Thanks for the quick reaction.

> However, I don't understand the last line of your log.  After the second
> port reset, why isn't there another "port 1 high speed" line?  Why did the
> status change to 000000?  It should be 001005, like it was after the first
> reset.
I have aranged myself a USB2 protocol analyzer, so I'll check whats
happening on the bus.

> If possible you should move up to 2.6.11, or even better, 2.6.15.
I did fuzzle a bit in the ehci_reset as on some boards it complained
that ehci_reset failed...
I will port 2.6.15 later on but that's not a quick action for now.

I'll keep you posted when I discover what it is.

thanks,

Niels Sterrenburg

> On Wed, 15 Mar 2006, Niels Sterrenburg wrote:
>
>> Hi List members,
>>
>> I'm busy with board bringup for the company I work for.
>>
>> We have an ISP1561 OHCI/EHCI controller on the PCI bus.
>>
>> OHCI is working fine but EHCI gives some problems.
>>
>> On EHCI device connection is reported but enumeration
>> seems to fail as the driver is not called (usb2 eth device).
>>
>> I enabled EHCI_VERBOSE_DEBUG and this is what I see:
>> ------------------------------------------------------------------------
>> ehci_hcd 0000:00:05.2: irq status 0004 PCD
>> hub 1-0:1.0: state 5 ports 2 chg fffc evt 0002
>> ehci_hcd 0000:00:05.2: GetStatus port 1 status 001803 POWER sig=j  CSC
>> CONNECT
>> hub 1-0:1.0: port 1, status 0501, change 0001, 480 Mb/s
>> ehci_hcd 0000:00:05.2: GetStatus port 1 status 001801 POWER sig=j
>> CONNECT
>> ehci_hcd 0000:00:05.2: GetStatus port 1 status 001801 POWER sig=j
>> CONNECT
>> ehci_hcd 0000:00:05.2: GetStatus port 1 status 001801 POWER sig=j
>> CONNECT
>> ehci_hcd 0000:00:05.2: GetStatus port 1 status 001801 POWER sig=j
>> CONNECT
>> ehci_hcd 0000:00:05.2: GetStatus port 1 status 001801 POWER sig=j
>> CONNECT
>> hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x501
>> ehci_hcd 0000:00:05.2: port 1 reset
>> ehci_hcd 0000:00:05.2: port 1 high speed
>> ehci_hcd 0000:00:05.2: GetStatus port 1 status 001005 POWER sig=se0  PE
>> CONNECT
>> usb 1-1: new high speed USB device using ehci_hcd and address 3
>> ehci_hcd 0000:00:05.2: irq status 0001 INT
>> ehci_hcd 0000:00:05.2: port 1 reset
>> ehci_hcd 0000:00:05.2: irq status 0020 IAA
>> ehci_hcd 0000:00:05.2: GetStatus port 1 status 000000 sig=se0
>> ------------------------------------------------------------------------
>> I check most status values and all are as expected.
>> Interrupt are working as stated in the log.
>>
>> Any ideas how I can check where/how the enumeration fails ?
>
> The information should be in the log, just after the portion you showed
> above.
>
> However, I don't understand the last line of your log.  After the second
> port reset, why isn't there another "port 1 high speed" line?  Why did the
> status change to 000000?  It should be 001005, like it was after the first
> reset.
>
>> Where is the point that the driver for a new device is located
>> based on device ID ?
>
> It occurs after the device descriptors have been read, obviously.  The
> code for finding the driver actually resides in userspace, rather than the
> kernel (udev and the hotplug package).
>
>> thanks in advance,
>>
>> Niels Sterrenburg
>>
>> PS I'm using 2.6.10 based kernel for MIPS and I do NOT trust the
>> hardware
>> schematics yet.....
>
> There was an important change in USB device initialization between 2.6.10
> and 2.6.11; one of the delays was too short.  It caused problems for a
> number of people using EHCI controllers.  Perhaps it's affecting your
> status values.  If possible you should move up to 2.6.11, or even better,
> 2.6.15.
>
> Alan Stern
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting
> language
> that extends applications into web and mobile media. Attend the live
> webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> [email protected]
> To unsubscribe, use the last form field at:
> https://lists.sourceforge.net/lists/listinfo/linux-usb-users
>



-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users

Reply via email to