Hi,
On Tue, Nov 28, 2017 at 6:37 AM, Stefan Wahren wrote:
> Hi Doug,
>
> Doug Anderson hat am 30. Oktober 2017 um 18:14
> geschrieben:
>
> Hi,
>
> On Mon, Oct 30, 2017 at 1:32 AM, Felipe Balbi wrote:
>>
>
> Hi,
>
> Doug Anderson
Doug Anderson writes:
> Hi,
>
> On Mon, Oct 30, 2017 at 1:32 AM, Felipe Balbi wrote:
>>
>> Hi,
>>
>> Doug Anderson writes:
>>> Hi,
>>>
>>> On Sat, Oct 28, 2017 at 8:51 AM, Stefan Wahren
>>> wrote:
Hi
Hi,
On Mon, Oct 30, 2017 at 1:32 AM, Felipe Balbi wrote:
>
> Hi,
>
> Doug Anderson writes:
>> Hi,
>>
>> On Sat, Oct 28, 2017 at 8:51 AM, Stefan Wahren
>> wrote:
>>> Hi Doug,
>>>
>>> [add Felipe since this should go through his
Hi,
Doug Anderson writes:
> Hi,
>
> On Sat, Oct 28, 2017 at 8:51 AM, Stefan Wahren wrote:
>> Hi Doug,
>>
>> [add Felipe since this should go through his tree]
>
> Ah. Sorry Felipe! I know you've landed some dwc2 stuff in the past
No problems
Hi Doug,
[add Felipe since this should go through his tree]
i'm back from vacation and happy to see this patch.
> Douglas Anderson hat am 26. Oktober 2017 um 22:22
> geschrieben:
>
>
> On rk3288-veyron devices on Chrome OS it was found that plugging in an
>
On rk3288-veyron devices on Chrome OS it was found that plugging in an
Arduino-based USB device could cause the system to lockup, especially
if the CPU Frequency was at one of the slower operating points (like
100 MHz / 200 MHz).
Upon tracing, I found that the following was happening:
* The USB