All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Anderson <dianders@chromium.org>
To: Yunzhi Li <lyz@rock-chips.com>
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: Wed, 11 Nov 2015 16:22:11 -0800	[thread overview]
Message-ID: <CAD=FV=XtvHxchGp2y5mvoAdeLPN5WAQz2jbC5Cc50+bybffK9A@mail.gmail.com> (raw)
In-Reply-To: <563C7B48.2020308@rock-chips.com>

John,

On Fri, Nov 6, 2015 at 2:04 AM, Yunzhi Li <lyz@rock-chips.com> wrote:
> hi John ,
>
>   As we talked yesterday, I tried to fix the split schedule sequence. This
> patch will
> avoid scheduling SSPLIT-IN packet for another device between
> SSPLIT-OUT-begin and
> SSPLIT-OUT-end, now the keyboard and Jebra audio speaker could work together
> well, but
> I'm not sure if this is exactly the right way to schedule split transfers
> and if there
> is any dide effect with this patch. Please help review this patch. Thanks.
>
>> 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(+)

Did you have any thoughts on this patch?  Although this patch didn't
fix the problems I was seeing with the Microsoft Wireless Keyboard
(see the patch I sent out earlier which does seem to fix it), I can
confirm that in a different setup (HUB goes to USB audio + mouse) that
this patch does fix some problems.

That being said, it feels to me like a band-aid rather than an actual
fix (I'm talking out of my rear end, though, since my USB experience
is lacking at best).  It feels like perhaps we're just not keeping
track the xact_pos correctly, but of course I don't know that for
sure...

Anyway, just fishing...  ;)

-Doug

  reply	other threads:[~2015-11-12  0:22 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 [this message]
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='CAD=FV=XtvHxchGp2y5mvoAdeLPN5WAQz2jbC5Cc50+bybffK9A@mail.gmail.com' \
    --to=dianders@chromium.org \
    --cc=John.Youn@synopsys.com \
    --cc=caesar.wang@rock-chips.com \
    --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=lyz@rock-chips.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.