[lkml]   [2008]   [Mar]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [RFC][PATCH] PM: Make PM core handle device registrations concurrent with suspend/hibernation
    On Tue, 4 Mar 2008, Rafael J. Wysocki wrote:

    > > It's not clear that we want to have this check. It would cause
    > > problems if the device ordering got mixed up by device_move(), which is
    > > pretty much the only way it could be triggered.
    > Well, isn't it actually dangerous to suspend parents before their children?
    > What happens, for example, if putting the parent into D3 causes power to be
    > cut from the children and then we attempt to suspend them?

    It depends on the devices involved. For PCI devices, obviously there
    will be problems of the sort you described. But for other devices
    there might not be.

    For example, the USB Bluetooth driver will sometimes create a new TTY
    device and then move the existing Bluetooth device underneath it (this
    description is oversimplified and probably wrong in some important
    respects, but you get the idea). Suspending the Bluetooth device
    before suspending the TTY won't cause any power-related problems,
    because a TTY is a purely logical device with no power implications at

    There might still be logical problems, of course... We need to add a
    mechanism for reordering the dpm_active list when device_move() is
    called. But first we need to get in touch with the people using
    device_move() -- basically just Marcel and Cornelia -- and see what
    sort of mechanism they will need.

    Alan Stern

     \ /
      Last update: 2008-03-05 17:07    [W:0.019 / U:4.900 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site