[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <10185436.tRUJHEj2GK@phil>
Date: Tue, 13 Sep 2016 16:30:32 +0200
From: Heiko Stuebner <heiko@...ech.de>
To: ayaka <ayaka@...lik.info>
Cc: linux-usb@...r.kernel.org, John.Youn@...opsys.com, kishon@...com,
felipe.balbi@...ux.intel.com, mark.rutland@....com,
devicetree@...r.kernel.org, gregkh@...uxfoundation.org,
linux-kernel@...r.kernel.org, linux-rockchip@...ts.infradead.org,
robh+dt@...nel.org, randy.li@...k-chips.com
Subject: Re: [RESEND PATCH v7 0/4] the fix for the USB HOST1 at rk3288 platform
Am Dienstag, 13. September 2016, 19:26:03 CEST schrieb ayaka:
> On 09/13/2016 07:06 PM, Heiko Stuebner wrote:
> > Hi Randy,
> >
> > could you check if the other host-only dwc2 are also affected by this
> > (rk3188, rk3036) please? Because they also seem to act up in some strange
> > way
> But I don't have those board currently. I would arrange them anyway.
> Btw, I would send a new version to correct the fault reported by the
> auto build machine.
What I meant was, if you could check with some hardware-people first, if the
other host-only dwc2 are supposedly also affected. Right now I'm trying to
determine if this effect is somehow related with the usb debounce issue
I'm seeing with some recent dwc2 patches [0].
Heiko
[0] http://lists.infradead.org/pipermail/linux-rockchip/2016-September/012141.html
https://git.kernel.org/cgit/linux/kernel/git/balbi/usb.git/commit/?h=testing/next&id=2938fc63e0c26bf694436ac81bc776c8b7eced0c
Powered by blists - more mailing lists