public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham-oKK1aGe2n869koe0gwxAeg@public.gmane.org>
To: Stephan Krings <Stephan.Krings-Mmb7MZpHnFY@public.gmane.org>
Cc: Rob Miller <rob-7HoZ3oJp7ZtBDgjK7y7TUQ@public.gmane.org>,
	ACPI List
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: ACPI - SWSUSP interaction
Date: Fri, 09 May 2003 20:27:43 +1200	[thread overview]
Message-ID: <1052389484.1754.33.camel@laptop-linux> (raw)
In-Reply-To: <16058.16.254227.882114-/D6BEnooUbBSBwh6+m2SNzw7hsPlABbXrfATN7qnIZ4@public.gmane.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

      parent reply	other threads:[~2003-05-09  8:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07 14:33 ACPI - SWSUSP interaction Rob Miller
     [not found] ` <Pine.LNX.4.21.0305071429500.7835-100000-fIJwbSqd/OutujjWdiIZrQ@public.gmane.org>
2003-05-08  6:58   ` Stephan Krings
     [not found]     ` <16058.16.254227.882114-/D6BEnooUbBSBwh6+m2SNzw7hsPlABbXrfATN7qnIZ4@public.gmane.org>
2003-05-09  8:27       ` Nigel Cunningham [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1052389484.1754.33.camel@laptop-linux \
    --to=ncunningham-okk1age2n869koe0gwxaeg@public.gmane.org \
    --cc=Stephan.Krings-Mmb7MZpHnFY@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=rob-7HoZ3oJp7ZtBDgjK7y7TUQ@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox