Re: Oops with dwc3 in device mode and functionfs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Vincent Pelletier <plr.vincent@xxxxxxxxx> writes:
> Hello,
>
> On Sun, Mar 26, 2017 at 9:20 PM, Andy Shevchenko
> <andriy.shevchenko@xxxxxxxxxxxxxxx> wrote:
>> On Sat, 2017-03-25 at 08:06 +0900, Vincent Pelletier wrote:
>>> FWIW, at home enumeration happens much more reliably behind a hub than
>>> directly on a host (both being xHCI). Maybe my edison board has some
>>> electrical issue a hub would tolerate better ?
>
> Re-reading what I wrote, I realize my vocabulary is misleading.
> Rephrasing for the record:
>
> Enumeration (HS chirp, bus address attribution) typically works, even
> directly on an xHCI. It is SET_CONFIGURATION (including the one done
> by the kernel after enumerating and before any driver tries to access
> the device) which very often fails on an xHCI, but very often succeeds
> when a hub (in my case, USB3) is inserted between the edison and the
> same xHCI.

I noticed that too and I still have no idea what's going on :-s

-- 
balbi

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux