All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 2/6] suspend: switch acpi s3 to new infrastructure.
Date: Thu, 9 Feb 2012 13:14:19 +0200	[thread overview]
Message-ID: <20120209111419.GG18866@redhat.com> (raw)
In-Reply-To: <4F33A541.6080401@redhat.com>

On Thu, Feb 09, 2012 at 11:51:45AM +0100, Gerd Hoffmann wrote:
>   Hi,
> 
> >>                 Pretend that resume was caused by power button */
> >>              pm1a->sts |=
> >>                  (ACPI_BITMASK_WAKE_STATUS | ACPI_BITMASK_POWER_BUTTON_STATUS);
> > Here we should report real reason for a wakeup (if it can be reported in
> > mp1sts that is).
> 
> These are available I guess?
> 
Yes. Once those defines had the same names as ACPI spec, but some kind soul
renamed them to be more "descriptive". So forgive me if I will use names
that you actually can lookup in ACPI spec.

> /* PM1x_STS */
> #define ACPI_BITMASK_TIMER_STATUS               0x0001
> #define ACPI_BITMASK_BUS_MASTER_STATUS          0x0010
> #define ACPI_BITMASK_GLOBAL_LOCK_STATUS         0x0020
> #define ACPI_BITMASK_POWER_BUTTON_STATUS        0x0100
> #define ACPI_BITMASK_SLEEP_BUTTON_STATUS        0x0200
> #define ACPI_BITMASK_RT_CLOCK_STATUS            0x0400
> #define ACPI_BITMASK_PCIEXP_WAKE_STATUS         0x4000  /* ACPI 3.0 */
> #define ACPI_BITMASK_WAKE_STATUS                0x8000
> 
Only three of those are actually wakeup source related:
PWRBTN_STS (bit 8)
RTC_STS (bit 10)
PCIEXP_WAKE_STS (bit 14)

And of course if system was awoken WAK_STS (bit 15) should be set too.

> What do they mean?  How would the rtc wakeup be tagged?  Set
> ACPI_BITMASK_RT_CLOCK_STATUS?  Anything I can use for ps/2 kbd/mouse
> wakeup?  What do you suggest to do when there is nothing usable (such as
> qemu monitor command which simply doesn't exist on real hardware)?
> 
RTC will set RTC_STS. In other reply I suggested to use PWRBTN_STS for
monitor command wakeup. Other devices are more complicated :( They have
to provide _PRW (Power Resources for Wake) method in the device
description in DSDT. This method, among other things, specifies which
bit in GPE (and which GPE) correspond to the device.

--
			Gleb.

WARNING: multiple messages have this Message-ID (diff)
From: Gleb Natapov <gleb@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: xen-devel@lists.xensource.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v3 2/6] suspend: switch acpi s3 to new infrastructure.
Date: Thu, 9 Feb 2012 13:14:19 +0200	[thread overview]
Message-ID: <20120209111419.GG18866@redhat.com> (raw)
In-Reply-To: <4F33A541.6080401@redhat.com>

On Thu, Feb 09, 2012 at 11:51:45AM +0100, Gerd Hoffmann wrote:
>   Hi,
> 
> >>                 Pretend that resume was caused by power button */
> >>              pm1a->sts |=
> >>                  (ACPI_BITMASK_WAKE_STATUS | ACPI_BITMASK_POWER_BUTTON_STATUS);
> > Here we should report real reason for a wakeup (if it can be reported in
> > mp1sts that is).
> 
> These are available I guess?
> 
Yes. Once those defines had the same names as ACPI spec, but some kind soul
renamed them to be more "descriptive". So forgive me if I will use names
that you actually can lookup in ACPI spec.

> /* PM1x_STS */
> #define ACPI_BITMASK_TIMER_STATUS               0x0001
> #define ACPI_BITMASK_BUS_MASTER_STATUS          0x0010
> #define ACPI_BITMASK_GLOBAL_LOCK_STATUS         0x0020
> #define ACPI_BITMASK_POWER_BUTTON_STATUS        0x0100
> #define ACPI_BITMASK_SLEEP_BUTTON_STATUS        0x0200
> #define ACPI_BITMASK_RT_CLOCK_STATUS            0x0400
> #define ACPI_BITMASK_PCIEXP_WAKE_STATUS         0x4000  /* ACPI 3.0 */
> #define ACPI_BITMASK_WAKE_STATUS                0x8000
> 
Only three of those are actually wakeup source related:
PWRBTN_STS (bit 8)
RTC_STS (bit 10)
PCIEXP_WAKE_STS (bit 14)

And of course if system was awoken WAK_STS (bit 15) should be set too.

> What do they mean?  How would the rtc wakeup be tagged?  Set
> ACPI_BITMASK_RT_CLOCK_STATUS?  Anything I can use for ps/2 kbd/mouse
> wakeup?  What do you suggest to do when there is nothing usable (such as
> qemu monitor command which simply doesn't exist on real hardware)?
> 
RTC will set RTC_STS. In other reply I suggested to use PWRBTN_STS for
monitor command wakeup. Other devices are more complicated :( They have
to provide _PRW (Power Resources for Wake) method in the device
description in DSDT. This method, among other things, specifies which
bit in GPE (and which GPE) correspond to the device.

--
			Gleb.

  reply	other threads:[~2012-02-09 11:14 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 11:00 [Qemu-devel] [PATCH v3 0/6] initial suspend support Gerd Hoffmann
2012-02-08 11:00 ` Gerd Hoffmann
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 1/6] suspend: add infrastructure Gerd Hoffmann
2012-02-08 11:00   ` Gerd Hoffmann
2012-02-09  8:48   ` [Qemu-devel] " Gleb Natapov
2012-02-09  8:48     ` Gleb Natapov
2012-02-09 10:45     ` [Qemu-devel] " Gerd Hoffmann
2012-02-09 10:45       ` Gerd Hoffmann
2012-02-09 11:19       ` [Qemu-devel] " Gleb Natapov
2012-02-09 11:19         ` Gleb Natapov
2012-02-09 12:02         ` [Qemu-devel] " Gerd Hoffmann
2012-02-09 12:02           ` Gerd Hoffmann
2012-02-09 12:37           ` [Qemu-devel] " Gleb Natapov
2012-02-09 12:37             ` Gleb Natapov
2012-02-09 12:46             ` [Qemu-devel] " Gerd Hoffmann
2012-02-09 12:46               ` Gerd Hoffmann
2012-02-09 13:17               ` [Qemu-devel] " Gleb Natapov
2012-02-09 13:17                 ` Gleb Natapov
2012-02-09 13:29                 ` [Qemu-devel] " Gerd Hoffmann
2012-02-09 13:29                   ` Gerd Hoffmann
2012-02-09 16:00                   ` [Qemu-devel] " Gerd Hoffmann
2012-02-09 16:00                     ` Gerd Hoffmann
2012-02-09 16:05                     ` [Qemu-devel] " Gleb Natapov
2012-02-09 16:05                       ` Gleb Natapov
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 2/6] suspend: switch acpi s3 to new infrastructure Gerd Hoffmann
2012-02-08 11:00   ` Gerd Hoffmann
2012-02-09  8:53   ` [Qemu-devel] " Gleb Natapov
2012-02-09  8:53     ` Gleb Natapov
2012-02-09 10:51     ` [Qemu-devel] " Gerd Hoffmann
2012-02-09 10:51       ` Gerd Hoffmann
2012-02-09 11:14       ` Gleb Natapov [this message]
2012-02-09 11:14         ` Gleb Natapov
2012-02-09 11:13   ` [Qemu-devel] [Xen-devel] " Stefano Stabellini
2012-02-09 11:13     ` Stefano Stabellini
2012-02-09 11:17   ` [Qemu-devel] " Paolo Bonzini
2012-02-09 11:17     ` Paolo Bonzini
2012-02-09 12:31     ` [Qemu-devel] " Gleb Natapov
2012-02-09 12:31       ` Gleb Natapov
2012-02-09 12:47       ` [Qemu-devel] " Paolo Bonzini
2012-02-09 12:47         ` Paolo Bonzini
2012-02-09 12:53         ` [Qemu-devel] " Gleb Natapov
2012-02-09 12:53           ` Gleb Natapov
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 3/6] suspend: add system_wakeup monitor command Gerd Hoffmann
2012-02-08 11:00   ` Gerd Hoffmann
2012-02-09  8:54   ` [Qemu-devel] " Gleb Natapov
2012-02-09  8:54     ` Gleb Natapov
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 4/6] suspend: make ps/2 devices wakeup the guest Gerd Hoffmann
2012-02-08 11:00   ` Gerd Hoffmann
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 5/6] suspend: make serial ports " Gerd Hoffmann
2012-02-08 11:00   ` Gerd Hoffmann
2012-02-08 11:00 ` [Qemu-devel] [PATCH v3 6/6] suspend: make rtc alarm " Gerd Hoffmann
2012-02-08 11:00   ` Gerd Hoffmann
2012-02-09  8:56   ` [Qemu-devel] " Gleb Natapov
2012-02-09  8:56     ` Gleb Natapov
2012-02-09 12:00     ` [Qemu-devel] " Gerd Hoffmann
2012-02-09 12:00       ` Gerd Hoffmann
2012-02-09 12:24       ` [Qemu-devel] " Gleb Natapov
2012-02-09 12:24         ` Gleb Natapov

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=20120209111419.GG18866@redhat.com \
    --to=gleb@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=xen-devel@lists.xensource.com \
    /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.