From: Romit Dasgupta <romit@ti.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: "Menon, Nishanth" <nm@ti.com>, linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 00/10 V5] omap3: pm: introduce support for 3630 OPPs
Date: Fri, 18 Dec 2009 15:56:37 +0530 [thread overview]
Message-ID: <4B2B58DD.6020901@ti.com> (raw)
In-Reply-To: <87tyvp60p6.fsf@deeprootsystems.com>
>>> [...]
>>>
>>>
>>>> To facilitate the ongoing discussions on OPP rework, and to have a
>>>> common base, this series is available as a branch in my linux-omap-pm
>>>> repo[1].
>>>>
<snip>
>
> Yes, I'm in the process cleaning that up.
>
> Once I get some of that cleanup done, I plan to rebase your OPP V5 and
> include it in the PM branch.
> I tried the latest HEAD on pm-wip-opp. Looks like the cpufreq tables are not
initialized because are not initializing {mpu|dsp|l3}_opps. Looks like the
comment on the latest commit is to use OPP APIs directly. Is there any patch
currently on that direction? Otherwise in the pm-wip-opp branch cpufreq is broken.
Thanks,
-Romit
next prev parent reply other threads:[~2009-12-18 10:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PATCH 02/10 V4] omap3: pm: introduce opp accessor functions>
2009-12-12 5:00 ` [PATCH 00/10 V5] omap3: pm: introduce support for 3630 OPPs Nishanth Menon
2009-12-12 5:00 ` [PATCH 02/10 V5] omap3: pm: introduce opp accessor functions Nishanth Menon
2009-12-12 5:00 ` [PATCH 03/10 V5] omap3: pm: use opp accessor functions for omap34xx Nishanth Menon
2009-12-12 5:00 ` [PATCH 09/10 V5] omap3: pm: introduce 3630 opps Nishanth Menon
2009-12-16 19:59 ` [PATCH 00/10 V5] omap3: pm: introduce support for 3630 OPPs Kevin Hilman
2009-12-16 22:37 ` Kevin Hilman
2009-12-17 3:22 ` Menon, Nishanth
2009-12-17 16:10 ` Kevin Hilman
2009-12-18 10:26 ` Romit Dasgupta [this message]
2009-12-18 16:04 ` 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=4B2B58DD.6020901@ti.com \
--to=romit@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox