At Tue, 19 May 2015 19:42:55 +0200,
Oliver Neukum wrote:
>
> On Tue, 2015-05-19 at 19:13 +0200, Takashi Iwai wrote:
> > At Tue, 19 May 2015 10:26:46 -0400 (EDT),
> > Alan Stern wrote:
> > >
> > > > > > Of just have request_firmware()
> > > > > > actually sleep until userspace is ready. Seriously
This series adds USB PHYs and EHCI host drivers for the Marvell PXA1928
SOC.
The OTG block is based on ChipIdea and works with the "chipidea,usb2"
compatible driver as is just by adding the PHY driver. Yay! After more
testing it turns out the EHCI host is also based on ChipIdea too. So
this vers
On Tue, May 19, 2015 at 01:21:30PM -0400, Alan Stern wrote:
> This strongly suggests that the problem lies in the hubs (or in one of
> them). Something caused a hub to disconnect, and when that happened
> all of the serial ports downstream from that hub went along for the
> ride.
Hi Alan, than
Hi Alan,
I am not convinced. Now we are hacking the Bluetooth core layer
(which has nothing to do with the drivers suspend/resume or
probe) to do something different so that we do not see this
warning.
I can not do anything about the platform in question choosing a
>
Some USB drivers have a logic at the VB buffer handling like:
if (in_interrupt())
BUG();
Use, instead:
BUG_ON(in_interrupt());
Btw, this logic looks weird on my eyes. We should convert them
to use VB2, in order to avoid those crappy things.
Signed-off-by: Mauro Car
