From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932333AbdADAjp (ORCPT ); Tue, 3 Jan 2017 19:39:45 -0500 Received: from smtprelay2.synopsys.com ([198.182.60.111]:42437 "EHLO smtprelay.synopsys.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752992AbdADAjX (ORCPT ); Tue, 3 Jan 2017 19:39:23 -0500 Subject: Re: [PATCH 0/5 v2] Fixes and workarounds for dwc2 on HiKey board To: John Stultz , lkml References: <1483473157-16678-1-git-send-email-john.stultz@linaro.org> From: John Youn CC: Wei Xu , Guodong Xu , "Amit Pundir" , Rob Herring , John Youn , Vardan Mikayelyan , Douglas Anderson , Chen Yu , Kishon Vijay Abraham I , Felipe Balbi , Greg Kroah-Hartman , Linux USB List Message-ID: <8c137989-efe0-006a-92bc-0459feb51087@synopsys.com> Date: Tue, 3 Jan 2017 16:31:22 -0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.9.138.146] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 1/3/2017 12:05 PM, John Stultz wrote: > On Tue, Jan 3, 2017 at 11:52 AM, John Stultz 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