Re: [RESEND patch 2.6.25] ACPI uses device_may_wakeup() policy inputs

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

 



On Tue, 29 Apr 2008, David Brownell wrote:

> > Indeed, it's easy to imagine a situation where somebody suspends their 
> > laptop and then unplugs a USB mouse, thereby causing a wakeup event.
> 
> It's also easy to imagine getting used to unplugging
> such devices *first* ... :)

Maybe.  But people aren't likely to unplug the mouse first if
suspending the laptop is done by clicking on a "Suspend" button.  :-)

Or consider the case of a flash drive with a mounted filesystem.  You 
can't safely unplug it before suspending, but you can safely unplug it 
after suspending (provided you remember to plug it back in before 
resuming).

Besides, people will complain that the [insert your choice] operating 
system doesn't make them remember to unplug USB devices before 
suspending, so why should Linux?

> > I suspect many PCI devices should be disabled for remote wakeup during 
> > system sleeps.
> 
> I wouldn't say that it's "PCI devices".  Remember, these
> patches only change ACPI behavior ... making it act more
> like non-ACPI systems.  If there's any change, in defaults
> it should not be a global "for all PCI devices" one ... it
> should be limited (and temporary!) for some ACPI devices.

I wasn't talking about defaults; I was talking about the settings 
people will find most useful.

> The situation is that *currently* ACPI is configured so
> that it's acts unlike non-ACPI systems:  wakeup isn't
> enabled.  And in at least some systems, it doesn't work
> when it's enabled either.
> 
> One can argue about how to deal with that breakage.  It
> seems likely to me that -- since this ACPI wakeup code
> has hardly ever been used on Linux -- using it will turn
> up bugs in the ACPI stack.  At which point a significant
> question is:  how are those bugs ever going to be found
> and fixed, if ACPI never actually turns on its wakeup
> mechanisms?

None of this is in dispute.

I'm simply pointing out that until common userspace tools are available
to change the wakeup behavior from the default "Always on if it's
available", people will run into problems and complain about
"regressions".

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