On 02/19/2016 10:11 AM, Chin Liang See wrote:
> On Thu, 2016-02-04 at 12:42 +0100, Marek Vasut wrote:
>> On Thursday, January 14, 2016 at 04:20:12 PM, Marek Vasut wrote:
>>> On Thursday, January 14, 2016 at 03:50:18 PM, Chin Liang See wrote:
On Wed, 2016-01-13 at 16:22 +0100, Marek Vasut
On Thu, 2016-02-04 at 12:42 +0100, Marek Vasut wrote:
> On Thursday, January 14, 2016 at 04:20:12 PM, Marek Vasut wrote:
> > On Thursday, January 14, 2016 at 03:50:18 PM, Chin Liang See wrote:
> > > On Wed, 2016-01-13 at 16:22 +0100, Marek Vasut wrote:
> > >
> > > Continue some troubleshooting
On Thursday, January 14, 2016 at 04:20:12 PM, Marek Vasut wrote:
> On Thursday, January 14, 2016 at 03:50:18 PM, Chin Liang See wrote:
> > On Wed, 2016-01-13 at 16:22 +0100, Marek Vasut wrote:
> > > On Wednesday, January 13, 2016 at 04:18:43 PM, Chin Liang See wrote:
> > > > On Wed, 2016-01-13 at
On Thursday, January 14, 2016 at 03:50:18 PM, Chin Liang See wrote:
> On Wed, 2016-01-13 at 16:22 +0100, Marek Vasut wrote:
> > On Wednesday, January 13, 2016 at 04:18:43 PM, Chin Liang See wrote:
> > > On Wed, 2016-01-13 at 03:58 +0100, Marek Vasut wrote:
> > > > On Tuesday, January 05, 2016 at
On Wed, 2016-01-13 at 16:22 +0100, Marek Vasut wrote:
> On Wednesday, January 13, 2016 at 04:18:43 PM, Chin Liang See wrote:
> > On Wed, 2016-01-13 at 03:58 +0100, Marek Vasut wrote:
> > > On Tuesday, January 05, 2016 at 05:16:05 PM, Marek Vasut wrote:
> > > > On Tuesday, January 05, 2016 at
On Wednesday, January 13, 2016 at 04:18:43 PM, Chin Liang See wrote:
> On Wed, 2016-01-13 at 03:58 +0100, Marek Vasut wrote:
> > On Tuesday, January 05, 2016 at 05:16:05 PM, Marek Vasut wrote:
> > > On Tuesday, January 05, 2016 at 04:51:47 PM, Chin Liang See wrote:
> > > > On Tue, 2016-01-05 at
On Wed, 2016-01-13 at 03:58 +0100, Marek Vasut wrote:
> On Tuesday, January 05, 2016 at 05:16:05 PM, Marek Vasut wrote:
> > On Tuesday, January 05, 2016 at 04:51:47 PM, Chin Liang See wrote:
> > > On Tue, 2016-01-05 at 15:36 +0100, Marek Vasut wrote:
> > > > On Tuesday, January 05, 2016 at
On Tuesday, January 05, 2016 at 05:16:05 PM, Marek Vasut wrote:
> On Tuesday, January 05, 2016 at 04:51:47 PM, Chin Liang See wrote:
> > On Tue, 2016-01-05 at 15:36 +0100, Marek Vasut wrote:
> > > On Tuesday, January 05, 2016 at 06:00:04 AM, Chin Liang See wrote:
> > > > Per DesignWare USB OTG
On Tuesday, January 05, 2016 at 04:51:47 PM, Chin Liang See wrote:
> On Tue, 2016-01-05 at 15:36 +0100, Marek Vasut wrote:
> > On Tuesday, January 05, 2016 at 06:00:04 AM, Chin Liang See wrote:
> > > Per DesignWare USB OTG databook, driver should retry up to
> > > 3 times when transaction error
On Tue, 2016-01-05 at 15:36 +0100, Marek Vasut wrote:
> On Tuesday, January 05, 2016 at 06:00:04 AM, Chin Liang See wrote:
> > Per DesignWare USB OTG databook, driver should retry up to
> > 3 times when transaction error (hcint.xacterr) happen. But
> > the 3 times doesn't count when the response
On Tuesday, January 05, 2016 at 06:00:04 AM, Chin Liang See wrote:
> Per DesignWare USB OTG databook, driver should retry up to
> 3 times when transaction error (hcint.xacterr) happen. But
> the 3 times doesn't count when the response is nack
> (hcint.nak) or frame overrun (hcint.frmoverun)
>
>
Per DesignWare USB OTG databook, driver should retry up to
3 times when transaction error (hcint.xacterr) happen. But
the 3 times doesn't count when the response is nack
(hcint.nak) or frame overrun (hcint.frmoverun)
This patch solved the enumeration error as spotted at socfpga
cyclone5_socdk
12 matches
Mail list logo