linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: khilman@deeprootsystems.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC/PATCH 0/2] OMAP: PM: add "early" idle notifier chain
Date: Wed, 20 Oct 2010 16:38:44 -0700	[thread overview]
Message-ID: <1287617926-24308-1-git-send-email-khilman@deeprootsystems.com> (raw)

Based on previous idle notification series, starting at:

      [PATCH 1/3] OMAP: PM: formalize idle notifications

This series adds an additional "early" idle notifier chain triggered
early in the CPUidle path with interrupts enabled.

This allows users of "early" notifiers to use blocking calls.  While
in general, use of blocking calls in idle notifiers should be avoided,
the current runtime PM API can sleep/schedule so cannot be done from
atomic context.  Use of "early" notifiers allows driver/device code to
use the runtime PM API in their idle notifier callbacks.

RFC: note that patch 2 enables interrupts in the CPUidle path, causing
interrupts to be enabled during the governor state selection and
device idle detection.  What could go wrong here?

Kevin Hilman (2):
  OMAP: PM: add "early" idle notifications
  OMAP3: CPUidle: trigger early idle notification call chain

 arch/arm/mach-omap2/cpuidle34xx.c        |   27 ++++++++++++++++++++++++---
 arch/arm/mach-omap2/pm.c                 |   27 +++++++++++++++++++++++++++
 arch/arm/plat-omap/include/plat/common.h |    6 ++++++
 3 files changed, 57 insertions(+), 3 deletions(-)

-- 
1.7.2.1

             reply	other threads:[~2010-10-20 23:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-20 23:38 Kevin Hilman [this message]
2010-10-20 23:38 ` [RFC/PATCH 1/2] OMAP: PM: add "early" idle notifications Kevin Hilman
2010-10-20 23:38 ` [RFC/PATCH 2/2] OMAP3: CPUidle: trigger early idle notification call chain Kevin Hilman
2010-10-21  5:38   ` Sripathy, Vishwanath
2010-10-21 17:39     ` Kevin Hilman
2010-10-21 17:43   ` Kevin Hilman

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=1287617926-24308-1-git-send-email-khilman@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).