From: Yunzhi Li <lyz@rock-chips.com>
To: John.Youn@synopsys.com, dianders@chromium.org,
jwerner@google.com, dinguyen@opensource.altera.com,
yousaf.kaukab@intel.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, wulf@rock-chips.com,
kever.yang@rock-chips.com, caesar.wang@rock-chips.com,
huangtao@rock-chips.com
Cc: rockchip-discuss@chromium.org, Yunzhi Li <lyz@rock-chips.com>
Subject: [RFC] usb: dwc2: hcd: fix split schedule issue
Date: Fri, 6 Nov 2015 17:36:52 +0800 [thread overview]
Message-ID: <1446802612-5828-1-git-send-email-lyz@rock-chips.com> (raw)
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
--
2.0.0
next reply other threads:[~2015-11-06 9:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 9:36 Yunzhi Li [this message]
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
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=1446802612-5828-1-git-send-email-lyz@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
all inboxes | Powered by JetHome®