Re: Re: Possible problem with device_move()

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

 



On Tue, 31 Jul 2007, Rafael J. Wysocki wrote:

> > There is a dependency in the USB subsystem, wherein I need an EHCI
> > controller to be _resumed_ after its companion UHCI or OHCI
> > controllers.  This works out, thanks to the fact that manufacturers
> > tend to give the EHCI controller the largest PCI function number and
> > the Linux PCI core enumerates functions in numerical order.  This is
> > just pure luck, however, and if anything changed I'd have to add an
> > explicit fix.
> 
> That sounds really worrying to me.
> 
> The design appears to be very fragile if such things are possible, even in
> theory.

It wouldn't break the entire resume; it would only prevent the 
USB-Persist facility from working with non-high-speed devices.  So it's 
not quite as bad as it may seem.

Still, I suppose it would be best to add a "move device A to the end of
the dpm_active list" routine for use in this sort of situation.  This 
should be easy to do.

Alan Stern

_______________________________________________
linux-pm mailing list
linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linux-foundation.org/mailman/listinfo/linux-pm

[Index of Archives]     [Linux ACPI]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [CPU Freq]     [Kernel Newbies]     [Fedora Kernel]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux