From: Nishanth Menon <nm@ti.com>
To: Andrew Murray <amurray@mpc-data.co.uk>
Cc: "Cousson, Benoit" <b-cousson@ti.com>,
"Dasgupta, Romit" <romit@ti.com>,
linux-omap <linux-omap@vger.kernel.org>,
Kevin Hilman <khilman@deeprootsystems.com>
Subject: Re: [PATCH] omap3: pm: cpufreq: populate l3 opp1 again
Date: Thu, 28 Jan 2010 09:18:10 -0600 [thread overview]
Message-ID: <4B61AAB2.6050003@ti.com> (raw)
In-Reply-To: <0C997DD87CC88A4F86C897F52650B52B02807801@MOLSON.mpc-data.co.uk>
Hi,
Thanks for all the comments.
Andrew Murray had written, on 01/28/2010 08:00 AM, the following:
>> From: Cousson, Benoit [mailto:b-cousson@ti.com]
>> Sent: 28 January 2010 13:48
>> To: Dasgupta, Romit; Menon, Nishanth
>> Cc: linux-omap; Andrew Murray; Kevin Hilman
>> Subject: RE: [PATCH] omap3: pm: cpufreq: populate l3 opp1 again
>
>> I don't want to keep it. I just want to document it in order to
> explain
>> why the code is not aligned with the public doc.
>>
>> Andrew did ask the question so the answer might be useful for others
> as
>> well, hence a small comment on top of the CORE OPP list.
>>
>> Benoit
>
> I agree.
>
> I don't think it matters if the OPP 'OMAP_OPP_DEF' is there or not.
> Though as the OPPs differ to the hardware descriptions it should be
> documented - perhaps as suggested, by a comment.
>
> It is confusing when validating the power management software support -
> and the best place to look for the rationale is in the code.
>
> Andrew Murray
I did consider removing it, till i did a git grep...
> $ git grep VDD2_OPP
> arch/arm/mach-omap2/pm34xx.c: resource_lock_opp(VDD2_OPP);
> arch/arm/mach-omap2/pm34xx.c: resource_unlock_opp(VDD2_OPP);
> arch/arm/mach-omap2/resource34xx.c: } else if (res == VDD2_OPP) {
> arch/arm/mach-omap2/resource34xx.c: else if (res == VDD2_OPP)
> arch/arm/mach-omap2/resource34xx.c: ret = resource_set_opp_level(VDD2_OPP, target_level, 0);
> arch/arm/mach-omap2/smartreflex.c: target_opp_no = VDD2_OPP3;
Grrrr... SR is going to break if I were to do that OR my patch can
renumber them.
> arch/arm/mach-omap2/smartreflex.c: } else if (vdd == VDD2_OPP) {
> arch/arm/mach-omap2/smartreflex.c: else if (vdd == VDD2_OPP)
> arch/arm/mach-omap2/smartreflex.h:#define PRCM_VDD2_OPP1 (OMAP(AT_3430_ES2) | OTHER_ID_TYPE(ID_OPP) | \
> arch/arm/mach-omap2/smartreflex.h:#define PRCM_VDD2_OPP2 (OMAP(AT_3430_ES2) | OTHER_ID_TYPE(ID_OPP) | \
> arch/arm/mach-omap2/smartreflex.h:#define PRCM_VDD2_OPP3 (OMAP(AT_3430_ES2) | OTHER_ID_TYPE(ID_OPP) | \
> arch/arm/mach-omap2/smartreflex.h:#define PRCM_NO_VDD2_OPPS 3
> arch/arm/plat-omap/include/plat/omap34xx.h:#define VDD2_OPP 0x2
> arch/arm/plat-omap/include/plat/omap34xx.h:#define VDD2_OPP1 0x1
> arch/arm/plat-omap/include/plat/omap34xx.h:#define VDD2_OPP2 0x2
> arch/arm/plat-omap/include/plat/omap34xx.h:#define VDD2_OPP3 0x3
All these should go away as well.. I missed these in my pm-wip-opp
patchset..
Do we want to do this now(DISCLAIMER: I am not volunteering{yet} ;) )?
OR do we want to wait till the current planned SR/SRF cleanups are complete?
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2010-01-28 15:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 5:41 [PATCH] omap3: pm: cpufreq: populate l3 opp1 again Nishanth Menon
2010-01-28 5:42 ` Nishanth Menon
2010-01-28 6:55 ` Romit Dasgupta
2010-01-28 13:24 ` Cousson, Benoit
2010-01-28 13:43 ` Dasgupta, Romit
2010-01-28 13:47 ` Cousson, Benoit
2010-01-28 14:00 ` Andrew Murray
2010-01-28 15:18 ` Nishanth Menon [this message]
2010-01-28 17:23 ` 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=4B61AAB2.6050003@ti.com \
--to=nm@ti.com \
--cc=amurray@mpc-data.co.uk \
--cc=b-cousson@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=romit@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 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.