Re: Oops with dwc3 in device mode and functionfs

Hi, Vincent Pelletier writes: > Hello, > > On Sun, Mar 26, 2017 at 9:20 PM, Andy Shevchenko > 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 ediso

Re: Oops with dwc3 in device mode and functionfs

Hello, On Sun, Mar 26, 2017 at 9:20 PM, Andy Shevchenko 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

Re: Oops with dwc3 in device mode and functionfs

On Sat, 2017-03-25 at 08:06 +0900, Vincent Pelletier wrote: > Hello Andy, Felipe, > > Sorry for the late reply. > > On Mon, Mar 20, 2017 at 6:23 PM, Felipe Balbi > wrote: > > Andy Shevchenko writes: > > > Can you check my latest snapshot? > > I built your github eds branch as of cfa21022e (bas

Re: Oops with dwc3 in device mode and functionfs

Hello Andy, Felipe, Sorry for the late reply. On Mon, Mar 20, 2017 at 6:23 PM, Felipe Balbi wrote: > Andy Shevchenko writes: >> Can you check my latest snapshot? I built your github eds branch as of cfa21022e (based on 4.11.0-rc3), but I still get enumeration issues (see below). I did not merg

Re: Oops with dwc3 in device mode and functionfs

Hi, Andy Shevchenko writes: > On Sat, 2017-01-07 at 04:07 +, Vincent Pelletier wrote: >> On Fri, 6 Jan 2017 15:21:17 +, Vincent Pelletier >> wrote: >> > The next issue is that often (>9 times out of 10) the dwc3 fails to >> > respond to the SET_CONFIGURATION standard request. As a resu

Re: Oops with dwc3 in device mode and functionfs

On Sat, 2017-01-07 at 04:07 +, Vincent Pelletier wrote: > On Fri, 6 Jan 2017 15:21:17 +, Vincent Pelletier > wrote: > > The next issue is that often (>9 times out of 10) the dwc3 fails to > > respond to the SET_CONFIGURATION standard request. As a result, only > > EP0 works. > > I capture

Re: Oops with dwc3 in device mode and functionfs

On Fri, 6 Jan 2017 15:21:17 +, Vincent Pelletier wrote: > The next issue is that often (>9 times out of 10) the dwc3 fails to > respond to the SET_CONFIGURATION standard request. As a result, only > EP0 works. I captured a successful enumeration, there are also corrupted pids: 002:03.271'422

Re: Oops with dwc3 in device mode and functionfs

On Tue, 3 Jan 2017 18:18:02 +0100, Vincent Pelletier wrote: > Sadly, this fix alone is not enough to get a functional device. I did > not investigate much yet, and need to get some sleep. I investigated more. The next issue is that often (>9 times out of 10) the dwc3 fails to respond to the SET_

Re: Oops with dwc3 in device mode and functionfs

Checking more, I think the 3 "do {...} while(--count)" loops in f_fs.c are wrong: they should be "while(count--){...}" ("git format-patch" attached, sorry, I'm on a dev-hostile mail client at the moment): - count covers function-specific endpoint, so it is 0 when no endpoint is declared, which lead

Re: Oops with dwc3 in device mode and functionfs

On Tue, 2017-01-03 at 17:00 +0200, Andy Shevchenko wrote: > On Tue, 2017-01-03 at 15:49 +0100, Vincent Pelletier wrote: > > Hello, > > > > I am hitting the following oops with 4.10-rc2 (on an intel edison, > > so > > this is with Andy's patchset[1] which is currently based on 4.10-rc2 > > and does

Re: Oops with dwc3 in device mode and functionfs

On Tue, 2017-01-03 at 15:49 +0100, Vincent Pelletier wrote: > Hello, > > I am hitting the following oops with 4.10-rc2 (on an intel edison, so > this is with Andy's patchset[1] which is currently based on 4.10-rc2 > and does not seem to touch usb code) with Felipe's fixes-for-v4.10-rc3 > merged on