Re: xhci data toggle out of sync

From: Hans Petter Selasky <hps_at_selasky.org>
Date: Thu, 21 Apr 2022 14:54:08 UTC
On 4/21/22 10:23, Mahesh Vardhamanaiah wrote:
> Hi HPS,
> 

Hi Mahesh,

> With few debug logs I do see that
> 
> xhci_configure_reset_endpoint:3958: epno = 3, ep_state = 3, drop = 0
> xhci_configure_reset_endpoint:3958: epno = 3, ep_state = 0, drop = 1
> 
> Do we need to do drop even if the ep_state is 0 ?
> 

My patch doesn't do that. See:

>  	switch (xhci_get_endpoint_state(udev, epno)) {
>  	case XHCI_EPCTX_0_EPSTATE_DISABLED:
> -                break;
> +		drop = 0;
> +		break;

I think the printout is seeing the endpoint state after the drop, and 
that is good!

Can you verify that there are no more bad data toggle values using the 
Beagle?

--HPS