All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brice Goglin <Brice.Goglin@ens-lyon.org>
To: Pavel Machek <pavel@suse.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	ACPI mailing list <acpi-devel@lists.sourceforge.net>,
	seife@suse.de, Len Brown <len.brown@intel.com>
Subject: Re: s4bios: does anyone use it?
Date: Sat, 05 Mar 2005 22:26:19 +0100	[thread overview]
Message-ID: <422A23FB.2010707@ens-lyon.org> (raw)
In-Reply-To: <20050305211747.GF1424@elf.ucw.cz>

Pavel Machek a écrit :
> Can you try cat /proc/acpi/sleep? If there's no difference between S4
> and S4bios, than you are probably just using plain S4...

puligny:~% cat /proc/acpi/sleep
S0 S1 S3 S4 S4bios S5

Where am I suppose to see a difference between S4 and S4Bios here ?


 From what I see in acpi_system_write_sleep in drivers/acpi/sleep/proc.c
4 uses software_suspend while 4b uses acpi_suspend(4)
(SOFTWARE_SUSPEND is set in my .config)
Is this code the right one ?

         /* Check for S4 bios request */
         if (!strcmp(str,"4b")) {
                 error = acpi_suspend(4);
                 goto Done;
         }
         state = simple_strtoul(str, NULL, 0);
#ifdef CONFIG_SOFTWARE_SUSPEND
         if (state == 4) {
                 error = software_suspend();
                 goto Done;
         }
#endif
         error = acpi_suspend(state);

> Yes, but it will take quite long to do it properly. pm_message_t
> framework needs to go in, first.

Ok, great! I'll be happy to test it soon :)

Brice

  reply	other threads:[~2005-03-05 21:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-05 19:14 s4bios: does anyone use it? Pavel Machek
2005-03-05 19:14 ` Pavel Machek
     [not found] ` <20050305191405.GA1463-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-05 21:08   ` Brice Goglin
2005-03-05 21:08     ` Brice Goglin
     [not found]     ` <422A1FB6.3000504-vYW+cPY1g1pg9hUCZPvPmw@public.gmane.org>
2005-03-05 21:17       ` Pavel Machek
2005-03-05 21:17         ` Pavel Machek
2005-03-05 21:26         ` Brice Goglin [this message]
2005-03-05 21:32           ` Pavel Machek
     [not found]             ` <20050305213236.GH1424-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-05 21:45               ` Brice Goglin
2005-03-05 21:45                 ` Brice Goglin
2005-03-05 22:01     ` Stefan Seyfried
2005-03-07 17:08   ` Bruno Ducrot
2005-03-07 17:08     ` [ACPI] " Bruno Ducrot
     [not found]     ` <20050307170852.GB31985-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2005-03-07 20:44       ` Pavel Machek
2005-03-07 20:44         ` [ACPI] " Pavel Machek
     [not found]         ` <20050307204401.GA15212-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-08  9:20           ` Bruno Ducrot
2005-03-08  9:20             ` [ACPI] " Bruno Ducrot
2005-03-05 21:39 ` Richard Mittendorfer
  -- strict thread matches above, loose matches on Subject: below --
2005-03-08  5:24 Li, Shaohua
2005-03-08  9:18 ` [ACPI] " Pavel Machek
     [not found]   ` <20050308091856.GB16436-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-08  9:42     ` Stefan Seyfried

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=422A23FB.2010707@ens-lyon.org \
    --to=brice.goglin@ens-lyon.org \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=seife@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.