[lkml]   [2004]   [Aug]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC] Fix Device Power Management States

    On Tue, 10 Aug 2004, Matthew Garrett wrote:

    > At the moment I'm struggling with the fact that the order of resumption
    > of system devices appears significant (ie, I get hangs on resume with
    > the stock kernel, but changing the list_for_each_entry in sysdev_resume
    > to list_for_each_entry_reverse makes things work) but there doesn't seem
    > to be any mechanism for providing proper ordering when there isn't a
    > tree structure. This also crops up with resuming my wireless hardware -
    > it tries to do a hotplug firmware load, but the IDE bus hasn't been
    > woken up yet.

    It's not that we need a tree; it's just that we need to take dependency
    information into account with system devices, and those aren't necessarily
    related to ancestry. That relates to the fact that not enough system
    devices have been converted, and not enough time has been spent, to really
    understand the dependency information enough to fix the model.

    As for the wireless device, I would suggest modifying the driver so that
    it retries the hotplug event. Or, perhaps it could be converted to use a
    mechanism in which events are not lost (kevents maybe?).

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:05    [W:2.708 / U:4.380 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site