RE: ehci scan_periodic loop time

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dears,

It is in the progress of verification with formal build. So far so good. But
I do not find out the USB 2.0 device that includes interrupt endpoint only
yet. I will try in advance. 
Please DO NOT add "Tested-by" for me when you would like to submit patch.
Thanks a lot !
:-))

Best Regards,
Brad
-----Original Message-----
From: Alan Stern [mailto:stern@xxxxxxxxxxxxxxxxxxx] 
Sent: Tuesday, March 29, 2011 10:46 PM
To: BradHuang
Cc: 'USB list'
Subject: RE: ehci scan_periodic loop time

On Tue, 29 Mar 2011, bradhuang wrote:

> Dears,
> 
> In fact, in my test scenario:
> Both interrupt endpoint and iso endpoint are working simultaneously. In
> scan_periodic(), case Q_TYPE_QH, it will add new qh when
> "list_empty(&qh->qtd_list)" is not ture in intr_deschedule(),

That should happen only when an interrupt transfer gets an error.  If 
the transfer completes normally and intr_deschedule() is called, then
list_empty(&qh->qtd_list) must be true.

>  so qh will be
> serviced more times. It is the root cause that takes more loop time. When
I
> apply your patch except the line I mentioned, it can work for all weekend
> normally. I will find the device (INT endpoint only) for testing in
advance.
> 
> Thanks a lot!

You're welcome.  Should I add a "Tested-by:" line for you when I submit 
the patch?

Alan Stern


--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux