On Mon, 2006-06-05 at 13:48 -0400, Adam Belay wrote:
> I've only tested this on a few x86 boxes. However, I think it's moving
> in the right direction for correctly suspending devices. It's worth
> mentioning that the PCI PM specification requires the device to be
> disabled before entering D3 (something that we fail to do before this
> patchset), and the vast majority of devices would end up in this state
> if we were using pci_set_power_state() in this function.
That should be done only for D3 though. Not other states.
> Unfortunately, far too many drivers still depend on this generic suspend
> call, when they should all implement their own suspend function. I
> would except pci_disable_device() issues to the the exception, and as
> such, device drivers should provide a ->suspend function that doesn't
> call pci_disable_device() when they know their hardware can be
> problematic.
>
> With that in mind, any thoughts on giving this a little time in -mm and
> seeing how it fares? If any problems come up, we could revert to a more
> conservative approach.
Problem is that you may end up disabling something like ... the ACPI
controller, and that will cause VERY BAD things with your BIOS when
actually trying to enter S3 or S4
Ben.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
