All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: Ming Lei <tom.leiming@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: [QUESTION] How to enable runtime PM
Date: Mon, 27 Sep 2010 08:24:04 -0700	[thread overview]
Message-ID: <87eicftdkb.fsf@deeprootsystems.com> (raw)
In-Reply-To: <AANLkTikAmbXPE=WX=D=g12xCVRUrmrXGY_qwuteCxbgX@mail.gmail.com> (Ming Lei's message of "Mon, 27 Sep 2010 10:07:07 +0800")

Ming Lei <tom.leiming@gmail.com> writes:

> Hi Kevin,
>
> I am interested in runtime pm implementation on OMAP3, and
> want to test this function on omap3-based beagle board, but seems
> no devices on omap3 Soc can support runtime pm(no __pm_runtime_*
> message found from 'dmesg' and rpm debug option is surely enabled)
> now after trying the two omap trees below:
>
>      git://git.kernel.org/pub/scm/linux/kernel/git/khilman/linux-omap-pm.git#pm-core
>      git://git.kernel.org/pub/scm/linux/kernel/git/tmlind/linux-omap-2.6.git#pm
>
> So, could you give me some guideline about how to bring up runtime pm
> on beagle? such as,
>
>                which git tree and branch should be used?
>                which option should be enabled?
>                or other things.

Hello,

Thanks for the interest in willing to experiment with runtime PM on
OMAP.

You're observations are correct.  The runtime PM core is ready, but none
of the devices have yet been adapted to the runtime PM API.  We will be
converting devices over to runtime PM over the next few merge windows,
with possibly some coming as soon as 2.6.37 (watchdog, UART, GPIO, i2c)

Kevin

      reply	other threads:[~2010-09-27 15:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-27  2:07 [QUESTION] How to enable runtime PM Ming Lei
2010-09-27 15:24 ` Kevin Hilman [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=87eicftdkb.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=tom.leiming@gmail.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.