From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: John Stultz <john.stultz@linaro.org>,
lkml <linux-kernel@vger.kernel.org>
Cc: John Stultz <john.stultz@linaro.org>,
Wei Xu <xuwei5@hisilicon.com>, Guodong Xu <guodong.xu@linaro.org>,
Amit Pundir <amit.pundir@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
John Youn <johnyoun@synopsys.com>,
Douglas Anderson <dianders@chromium.org>,
Chen Yu <chenyu56@huawei.com>,
Vardan Mikayelyan <mvardan@synopsys.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org
Subject: Re: [RFC][PATCH 0/5 v2] Fixes and workarounds for dwc2 on HiKey board
Date: Mon, 16 Jan 2017 12:29:16 +0200 [thread overview]
Message-ID: <878tqbnvr7.fsf@linux.intel.com> (raw)
In-Reply-To: <1481952713-29829-1-git-send-email-john.stultz@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
Hi,
John Stultz <john.stultz@linaro.org> writes:
> I just wanted to re-send my current queue of patches for dwc2
> controller on the HiKey board, as my last patchset ended up
> colliding with a number of changes that landed in the 4.10-rc
> merge window.
>
> I've fixed things up and validated these against HiKey. I also
> made a small change to one of the patches as suggested by Vardan.
>
> This does exclude my patchset[1] to add extcon support to dwc2,
> which John Youn suspects a pending rework of the dwc2 fifo init
> logic might make unnecssary (however, no such changes appeared
> to have landed in 4.10-rc, so I'm still using that patchset in
> my testing).
>
> I'm also out for the holidays after today, and while I suspect
> others are likely going to be out as well, I figured I'd send
> these out for a chance at review, rather then sit on them for
> two weeks. I'll resend after the new year addressing any
> feedback I do get though.
>
> Feedback would be greatly appreciated!
John Y, any comments?
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-01-16 10:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-17 5:31 [RFC][PATCH 0/5 v2] Fixes and workarounds for dwc2 on HiKey board John Stultz
2016-12-17 5:31 ` [RFC][PATCH 1/5 v2] usb: dwc2: Avoid sleeping while holding hsotg->lock John Stultz
2016-12-17 5:31 ` [RFC][PATCH 2/5 v2] usb: dwc2: Workaround case where GOTGCTL state is wrong John Stultz
2016-12-17 5:31 ` [RFC][PATCH 3/5 v2] usb: dwc2: Force port resume on switching to device mode John Stultz
2016-12-17 5:31 ` [RFC][PATCH 4/5 v2] usb: dwc2: Avoid suspending if we're in gadget mode John Stultz
2016-12-17 5:31 ` [RFC][PATCH 5/5 v2] usb: dwc2: Add a quirk to allow speed negotiation for Hisilicon Hi6220 John Stultz
2017-01-16 10:29 ` Felipe Balbi [this message]
2017-01-16 20:23 ` [RFC][PATCH 0/5 v2] Fixes and workarounds for dwc2 on HiKey board John Stultz
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=878tqbnvr7.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=amit.pundir@linaro.org \
--cc=chenyu56@huawei.com \
--cc=dianders@chromium.org \
--cc=gregkh@linuxfoundation.org \
--cc=guodong.xu@linaro.org \
--cc=john.stultz@linaro.org \
--cc=johnyoun@synopsys.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mvardan@synopsys.com \
--cc=robh+dt@kernel.org \
--cc=xuwei5@hisilicon.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