Re: Boot regression on Versatile Express TC2 after commit b2b49ccbdd

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

 



On Wed, 21 Jan 2015, Rafael J. Wysocki wrote:

> > > > If nothing happens, there are two possibilities: The hub doesn't 
> > > > support wakeup signalling, or the isp1760-hcd driver doesn't support 
> > > > it.  To tell the truth, it wouldn't be surprising if the second turns 
> > > > out to be the case.
> > > 
> > > How can this be determined?
> > > 
> > > According to /proc/interrupts, isp1760-hcd:usb1 no longer receive any 
> > > interrupts.  Wether or not it could is something I don't know.
> > 
> > I don't know either.  At this point, you have to ask a developer who is 
> > familiar with the isp1760 hardware and driver.  Perhaps one of the 
> > people on the CC: list can help.
> > 
> > At least you are able to boot your system now with the command-line 
> > option.  That's an improvement.
> 
> Well, assuming that the HCD driver doesn't support wakeup signaling,
> it would be good to have a way to indicate the lack of support for
> autosuspend to the USB core so as to avoid the user-visible breakage.
> 
> Do we have any means for that?

We could create a flag for it.  Right now there's no way to indicate
it; the USB stack assumes all host controller drivers fully support
wakeup signalling.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




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

  Powered by Linux