USB EHCI/OHCI experts
On omap-git v2.6.25-rc2, TI OMAP34xx EHCI controller, we are seeing a strange
behavior on a bulk OUT 512 byte transfer.
We can see through the CATC that the 512 byte goes out successfully but there
are many Turnaround/Timeout Errors and retries before the packet goes out
USB EHCI/OHCI experts
On omap-git v2.6.25-rc2, TI OMAP34xx EHCI controller, we are seeing a strange
behavior on a bulk OUT 512 byte transfer.
We can see through the CATC that the 512 byte goes out successfully but there
are many Turnaround/Timeout Errors and retries before the packet goes out
it when URB is submitted and the QH will have multiple transfer descriptors
dynamically created as per the request.
Now its it's a control EP0 URB, a QH would be created with Address=0 and tds
with setup token etc.
>
>Appreciate your help,
>vichy
>
>-Original Message--
>Sent: Monday, February 11, 2008 8:51 PM
>> Dear all:
>
>> 2. What is the "device address" used for in QH?
>
>There is no "device address" field in a QH -- at least, there isn't in
>uhci-hcd or ehci-hcd. Maybe other controller drivers do have such a
>field.
I have a doubt -
Referring to ehci sp
usb_kill_urb() ensures that URB is unlinked and callback is called.
My question is, what happens to the URB that is already scheduled by underlying
HCD and getting processed, and usb_kill_urb() is called?
What will be returned by completion handler for such an URB if it was bulk IN
and bulk O
Hi Oliver
>Sent: Monday, January 21, 2008 6:46 PM
>> >> I have a general query on EHCI manual suspend/resume behavior.
>> >>
>> >> For EHCI HCD, On doing a manual suspend of a device using sysfs
>> >> power/level, what happens of the
>> >already submitted URBs?
>> >>
>> >> are the URBs completed
Hi Oliver
>Sent: Monday, January 21, 2008 6:18 PM
>> I have a general query on EHCI manual suspend/resume behavior.
>>
>> For EHCI HCD, On doing a manual suspend of a device using sysfs power/level,
>> what happens of the
>already submitted URBs?
>>
>> are the URBs completed with whatever data ha
I have a general query on EHCI manual suspend/resume behavior.
For EHCI HCD, On doing a manual suspend of a device using sysfs power/level,
what happens of the already submitted URBs?
are the URBs completed with whatever data has been sent? Or
URB context is maintained and are restarted on a R
On Kernel 2.6.24,
I am trying Suspend/Resume on OMAP3430 EHCI controller with Netchip2280 High
speed test device.
Following is the behaviour:
#echo suspend > /sys/bus/usb/devices/2-2/power/level
# suspend root hub
On the bus, SOFs stop and device goes to Suspend [As expected]
#echo on
>From: David Brownell [mailto:[EMAIL PROTECTED]
>
>> The status of EHCI registers is as follows and the test does not complete.
>> The system is still up but no USB activity is happening.
>
>What do you mean? That you're watching the traffic on-the-wire,
>and nothing at all is happening? (I'm sur
On kernel 2.6.24-rc5(from omap-git) I am testing the EHCI controller on
OMAP34xx.
I have connected the device (netchip2280 + g_zero.ko ) to the EHCI controller.
Device side test:
On the gadget zero I run the IN test 6: ./testusb -a -t6 -s1024 -c100
OMAP EHCI HOST status:
On EHCI I can see that,
11 matches
Mail list logo
