public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Paul Walmsley <paul@pwsan.com>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	linux-pm@lists.linux-foundation.org, linux-omap@vger.kernel.org
Subject: Re: [linux-pm] Runtime PM discussion notes
Date: Sat, 30 Jul 2011 23:25:23 +0200	[thread overview]
Message-ID: <20110730212523.GA10450@elf.ucw.cz> (raw)
In-Reply-To: <201107302309.19169.rjw@sisk.pl>


> > > IIRC I solved it by just calling _PTS when sleepy Linux was
> > > enabled. It had side effect of lighting up moon icon, but otherwise
> > > seemed to work ok.
> > > 
> > > I do not think ACPI says what can and can not be done after _PTS...
> > 
> > Yes, it does.
> 
> And even if _PTS will work, you're certainly not supposed to execute _WAK
> with interrupts off.

It should be ok to execute _WAK in process context once system is
resumed. ... or maybe not executing _WAK at all. User can probably
live with moon icon lighted up.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2011-07-30 21:25 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTim=aunvBDLincgXX5yYNhvDTk+fhQ@mail.gmail.com>
     [not found] ` <201106102015.47146.rjw@sisk.pl>
     [not found]   ` <BANLkTimgiJGKASGx80=hTBPBQ52ttmp+Kw@mail.gmail.com>
     [not found]     ` <201106150048.43187.rjw@sisk.pl>
2011-06-23 14:51       ` Runtime PM discussion notes Paul Walmsley
2011-06-23 15:23         ` [linux-pm] " Alan Stern
2011-06-23 20:34           ` Rafael J. Wysocki
2011-06-24 19:53             ` Paul Walmsley
2011-06-24 22:27               ` Arve Hjønnevåg
2011-06-25  5:33                 ` Magnus Damm
2011-06-28 19:47                 ` Paul Walmsley
2011-07-09  4:06                   ` Mark Brown
2011-07-11  9:58                     ` Tony Lindgren
2011-07-11 11:04                       ` Mark Brown
2011-07-11 11:14                         ` Tony Lindgren
2011-07-11 11:26                           ` Mark Brown
2011-07-11 11:32                             ` Tony Lindgren
2011-07-13  7:17                             ` Paul Walmsley
2011-07-13  9:04                               ` Rafael J. Wysocki
2011-07-29 13:41                                 ` Pavel Machek
2011-07-29 19:52                                   ` Rafael J. Wysocki
2011-07-30 20:37                                     ` Pavel Machek
2011-07-30 21:05                                       ` Rafael J. Wysocki
2011-07-30 21:09                                         ` Rafael J. Wysocki
2011-07-30 21:25                                           ` Pavel Machek [this message]
2011-07-30 21:36                                             ` [linux-pm] " Rafael J. Wysocki
2011-07-30 22:09                                         ` Pavel Machek
2011-07-30 22:41                                           ` Rafael J. Wysocki
2011-06-25 13:51               ` [linux-pm] " Rafael J. Wysocki
2011-06-24 18:36           ` Paul Walmsley
2011-06-25 18:59             ` Alan Stern

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=20110730212523.GA10450@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=paul@pwsan.com \
    --cc=rjw@sisk.pl \
    /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