From: John Youn <John.Youn@synopsys.com>
To: John Stultz <john.stultz@linaro.org>,
lkml <linux-kernel@vger.kernel.org>
Cc: 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 <John.Youn@synopsys.com>,
Vardan Mikayelyan <Vardan.Mikayelyan@synopsys.com>,
Douglas Anderson <dianders@chromium.org>,
Chen Yu <chenyu56@huawei.com>,
Kishon Vijay Abraham I <kishon@ti.com>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linux USB List <linux-usb@vger.kernel.org>
Subject: Re: [PATCH 0/5 v2] Fixes and workarounds for dwc2 on HiKey board
Date: Tue, 3 Jan 2017 16:31:22 -0800 [thread overview]
Message-ID: <8c137989-efe0-006a-92bc-0459feb51087@synopsys.com> (raw)
In-Reply-To: <CALAqxLUdQtYezj4UyXCt7njBCKFO64A1Jg586hooj5dBGo+N0g@mail.gmail.com>
On 1/3/2017 12:05 PM, John Stultz wrote:
> On Tue, Jan 3, 2017 at 11:52 AM, John Stultz <john.stultz@linaro.org> wrote:
>> Hope everyone had a happy new years!
>>
>> I just wanted to send out my current queue of patches for dwc2
>> controller on the HiKey board for consideration for the 4.11
>> merge window.
>>
>> 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.
>
> John/Vardan: Just as a heads up, along with these patches, I'm also
> still using the "fix flags for DMA descriptor allocation in
> dwc2_hsotg_ep_enable" from Marek Szyprowski, as its not landed
This just hit Greg's tree and should be in -rc3.
> upstream, and I'm also still seeing the matching warning on
> dwc2_hsotg_ep_disable() on the free side, as I've not seen a fix for
> that yet.
Most of the team is out this week, so it might not be ready until next
week. Unfortunately we had some infrastructure issues which prevented
us from getting this out before the holidays.
Regards,
John
next prev parent reply other threads:[~2017-01-04 0:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-03 19:52 John Stultz
2017-01-03 19:52 ` [PATCH 1/5 v2] usb: dwc2: Avoid sleeping while holding hsotg->lock John Stultz
2017-01-03 19:52 ` [PATCH 2/5 v2] usb: dwc2: Workaround case where GOTGCTL state is wrong John Stultz
2017-01-03 19:52 ` [PATCH 3/5 v2] usb: dwc2: Force port resume on switching to device mode John Stultz
2017-01-03 19:52 ` [PATCH 4/5 v2] usb: dwc2: Avoid suspending if we're in gadget mode John Stultz
2017-01-03 19:52 ` [PATCH 5/5 v2] usb: dwc2: Add a quirk to allow speed negotiation for Hisilicon Hi6220 John Stultz
2017-01-03 20:05 ` [PATCH 0/5 v2] Fixes and workarounds for dwc2 on HiKey board John Stultz
2017-01-04 0:31 ` John Youn [this message]
2017-01-04 0:39 ` John Stultz
2017-01-11 22:08 ` John Youn
2017-01-11 22:39 ` John Stultz
2017-01-11 22:58 ` John Youn
2017-01-11 23:10 ` John Stultz
2017-01-11 23:16 ` John Youn
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=8c137989-efe0-006a-92bc-0459feb51087@synopsys.com \
--to=john.youn@synopsys.com \
--cc=Vardan.Mikayelyan@synopsys.com \
--cc=amit.pundir@linaro.org \
--cc=chenyu56@huawei.com \
--cc=dianders@chromium.org \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=guodong.xu@linaro.org \
--cc=john.stultz@linaro.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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
all inboxes | Powered by JetHome®