From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nigel Cunningham Subject: Re: ACPI - SWSUSP interaction Date: Fri, 09 May 2003 20:27:43 +1200 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <1052389484.1754.33.camel@laptop-linux> References: <16058.16.254227.882114@hotzenplotz.chateau-neukoelln.de> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-reply-to: <16058.16.254227.882114-/D6BEnooUbBSBwh6+m2SNzw7hsPlABbXrfATN7qnIZ4@public.gmane.org> Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Stephan Krings Cc: Rob Miller , ACPI List List-Id: linux-acpi@vger.kernel.org Hi. There's no interaction between swsusp and ACPI at present. Neither, I believe, should there be (2.5 is a different story, since it has the driver model). If it's possible for ACPI to properly check the status (and I'd be surprised if its not possible), it should do so rather than storing the state in a variable. Since its not done in this way at the moment, I'd _assume_ some deficiency(sp?) in the ACPI spec (rather than that Andy et al have tried to take a shortcut) or that it's done this way as an optimisation. Regards, Nigel On Thu, 2003-05-08 at 18:58, Stephan Krings wrote: > Hi, > > > In any event, I think there is an issue that one or more folk here may be > > able to help with. It appears to me that reads of at least the following > > /proc entries do not actually test the hardware state, but rely on > > detecting ACPI events to trigger changes in stored information: > > [ ... ] > > > Question 1: Is my conclusion above accurate, or have I run into an > > idiosyncrasy of the laptop? > > No, I can confirm your observation. I'm also using both ACPI and the > swsusp patches for 2.4. When the machine is suspended and the AC > adapter changes state, this change will not be recognized upon resume. > > I'd guess that the ACPI code stores the state somewhere in memory and > will only change it, when the ACPI BIOS generates events. > > I think the ACPI code should just reexamine some values after > resume. This will require quite a lot of integration between swsusp > and ACPI and I'm not sure, if this integration is already present. > > Regards, > > Stephan > > > > ------------------------------------------------------- > Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara > The only event dedicated to issues related to Linux enterprise solutions > www.enterpriselinuxforum.com > > _______________________________________________ > Acpi-devel mailing list > Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org > https://lists.sourceforge.net/lists/listinfo/acpi-devel -- Nigel Cunningham 495 St Georges Road South, Hastings 4201, New Zealand Be diligent to present yourself approved to God as a workman who does not need to be ashamed, handling accurately the word of truth. -- 2 Timothy 2:14, NASB. ------------------------------------------------------- Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara The only event dedicated to issues related to Linux enterprise solutions www.enterpriselinuxforum.com