[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.0901311652500.3067@localhost.localdomain>
Date: Sat, 31 Jan 2009 17:06:47 -0800 (PST)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: "Rafael J. Wysocki" <rjw@...k.pl>
cc: Parag Warudkar <parag.lkml@...il.com>,
Matt Carlson <mcarlson@...adcom.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: What should PCI core do during suspend-resume? (was: Re:
2.6.29-rc3: tg3 dead after resume)
On Sun, 1 Feb 2009, Rafael J. Wysocki wrote:
>
> All this leads to the conclusion that we should put devices into low power
> states with interrupts off and this seems to imply that we'll need to make the
> AML interpreter allow us to run AML with interrupts off.
How many devices actually have the _PS3 method (or whatever it is that we
end up executing)? We might be able to simply flag it, and say "ok, if we
have a _PS3 method, we'll have to suspend early, otherwise we can leave it
for a late suspend".
Definitely not perfect, but perhaps a way to get the safe thing on 99% of
all cases, and have to live with the horrid ACPI rules on some things.
I thought the _DSW thing is common for setting up wakeup, but _PSx is not.
But I have not looked at many ACPI tables in my life. I try to active
avoid it if I at all humanly can.
Linus
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists