From: Kevin Hilman <khilman@baylibre.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "Pali Rohár" <pali.rohar@gmail.com>,
"Sebastian Reichel" <sre@kernel.org>,
"Ivaylo Dimitrov" <ivo.g.dimitrov.75@gmail.com>,
"Pavel Machek" <pavel@ucw.cz>,
"Aaro Koskinen" <aaro.koskinen@iki.fi>,
"Nishanth Menon" <nm@ti.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Missing OMAP PM layer
Date: Mon, 25 Jan 2016 10:16:01 -0800 [thread overview]
Message-ID: <7hpowpr0da.fsf@baylibre.com> (raw)
In-Reply-To: <20160125163442.GU19432@atomide.com> (Tony Lindgren's message of "Mon, 25 Jan 2016 08:34:42 -0800")
Tony Lindgren <tony@atomide.com> writes:
> * Pali Rohár <pali.rohar@gmail.com> [160124 12:24]:
>> Hello,
>>
>> make menuconfig allows me to choose "OMAP PM layer selection" and the
>> only one option is CONFIG_OMAP_PM_NOOP "No-op/debug PM layer".
>>
>> What does it mean? Power manager is noop?
>>
>> I see that it has only two corresponding files in mainline kernel:
>> arch/arm/mach-omap2/omap-pm.h
>> arch/arm/mach-omap2/omap-pm-noop.c
>>
>> Nokia's kernels (for N900 and N950) had also:
>> arch/arm/mach-omap2/omap-pm-srf.c
>>
>> Can somebody explain it what happened with omap power management?
>>
>> Looks like that omap-pm.h provides some API, but the only implementation
>> is noop which do nothing.
>
> I believe none of that is needed any longer in mainline.
>
> Kevin, care to descrbibe what should be done here?
We had created the OMAP PM layer as a pluggable layer where we could
experiment with different approaches for adding constratints, etc. I
can't remember anymore what all was in there, but we gutted most of it
after switching to runtime PM.
The SRF was a "shared resource framework" that came out of a TI kernel
that was never accepted upstream either, but was one of the
implementation of the OMAP PM layer.
Kevin
prev parent reply other threads:[~2016-01-25 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 20:23 Missing OMAP PM layer Pali Rohár
2016-01-25 16:34 ` Tony Lindgren
2016-01-25 17:24 ` Pali Rohár
2016-01-25 18:16 ` 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=7hpowpr0da.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=aaro.koskinen@iki.fi \
--cc=ivo.g.dimitrov.75@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=sre@kernel.org \
--cc=tony@atomide.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.