From: Yunzhi Li <lyz@rock-chips.com>
To: Doug Anderson <dianders@chromium.org>
Cc: John Youn <John.Youn@synopsys.com>,
Julius Werner <jwerner@google.com>,
Dinh Nguyen <dinguyen@opensource.altera.com>,
"Kaukab, Yousaf" <yousaf.kaukab@intel.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
wulf <wulf@rock-chips.com>,
Kever Yang <kever.yang@rock-chips.com>,
caesar <caesar.wang@rock-chips.com>,
Tao Huang <huangtao@rock-chips.com>,
rockchip-discuss <rockchip-discuss@chromium.org>
Subject: Re: [RFC] usb: dwc2: hcd: fix split schedule issue
Date: Mon, 9 Nov 2015 17:57:29 +0800 [thread overview]
Message-ID: <56406E09.4030903@rock-chips.com> (raw)
In-Reply-To: <CAD=FV=UE+7c8oX4TrJExVFdALm6er0Tix_ApxOVEannKqo3Y9A@mail.gmail.com>
hi Doug
在 2015/11/7 7:56, Doug Anderson 写道:
> lyz@,
>
> On Fri, Nov 6, 2015 at 1:36 AM, Yunzhi Li <lyz@rock-chips.com> wrote:
>> Fix dwc2 split schedule sequence issue. Not schedule a SSPLIT_IN
>> packet between SSPLIT-begin and SSPLIT-end.
>>
>> Signed-off-by: Yunzhi Li <lyz@rock-chips.com>
>> ---
>> drivers/usb/dwc2/hcd.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/drivers/usb/dwc2/hcd.c b/drivers/usb/dwc2/hcd.c
>> index e79baf7..a32ed01 100644
>> --- a/drivers/usb/dwc2/hcd.c
>> +++ b/drivers/usb/dwc2/hcd.c
>> @@ -1122,6 +1122,10 @@ static void dwc2_process_periodic_channels(struct dwc2_hsotg *hsotg)
>> break;
>> }
>>
>> + if (qh->channel->xact_pos == DWC2_HCSPLT_XACTPOS_BEGIN ||
>> + qh->channel->xact_pos == DWC2_HCSPLT_XACTPOS_MID)
>> + break;
>> +
>> /*
>> * In Slave mode, stay on the current transfer until there is
>> * nothing more to do or the high-bandwidth request count is
> Just a quite note to say that this doesn't seem to resolve the weird
> errors I'm seeing with the "Microsoft Wireless Keyboard 2000" that I
> have. I see split transaction errors in a USB analyzer with just that
> hooked up behind a hub (don't even need any other USB devices).
>
> ...it is possible that there are two unrelated problems here, but it's
> also possible that there's some bigger root cause that will fix both
> of our problems. I've been poking at things a bit too, but so far no
> luck...
>
> -Doug
>
It seems that we are debugging two different issues, your new patch which rewrite
the microframe scheduler doesn't resolve my problem. My patch fix chrome-os issue
#46547 not related to the particular Microsoft keyboard any keyboard could be used
to reproduce the issue.
next prev parent reply other threads:[~2015-11-09 10:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 9:36 [RFC] usb: dwc2: hcd: fix split schedule issue Yunzhi Li
2015-11-06 10:04 ` Yunzhi Li
2015-11-12 0:22 ` Doug Anderson
2015-11-12 4:29 ` John Youn
2015-11-12 4:46 ` Doug Anderson
2015-11-13 5:05 ` John Youn
2015-11-14 0:33 ` Doug Anderson
2015-11-14 17:32 ` Alan Stern
2015-11-16 20:46 ` Julius Werner
2015-11-12 9:42 ` Yunzhi Li
2015-11-17 3:56 ` Doug Anderson
2015-11-06 23:56 ` Doug Anderson
2015-11-09 9:57 ` Yunzhi Li [this message]
2015-11-09 14:37 ` Doug Anderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56406E09.4030903@rock-chips.com \
--to=lyz@rock-chips.com \
--cc=John.Youn@synopsys.com \
--cc=caesar.wang@rock-chips.com \
--cc=dianders@chromium.org \
--cc=dinguyen@opensource.altera.com \
--cc=huangtao@rock-chips.com \
--cc=jwerner@google.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rockchip-discuss@chromium.org \
--cc=wulf@rock-chips.com \
--cc=yousaf.kaukab@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox