All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Kevin Hilman <khilman@deeprootsystems.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
	"K, Ambresh" <ambresh@ti.com>,
	"Cousson, Benoit" <b-cousson@ti.com>,
	Eduardo Valentin <eduardo.valentin@nokia.com>,
	Phil Carmody <ext-phil.2.carmody@nokia.com>,
	"Premi, Sanjeev" <premi@ti.com>,
	Tero Kristo <tero.kristo@nokia.com>,
	"Gopinath, Thara" <thara@ti.com>
Subject: Re: [PM-WIP-OPP][PATCH 1/2 v2] omap3: pm: cpufreq: BUG_ON cleanup
Date: Tue, 20 Apr 2010 18:48:25 -0500	[thread overview]
Message-ID: <4BCE3D49.20309@ti.com> (raw)
In-Reply-To: <87d3xtbskh.fsf@deeprootsystems.com>

Kevin Hilman had written, on 04/20/2010 06:41 PM, the following:
> Nishanth Menon <nm@ti.com> writes:
[..]

>>
>> Signed-off-by: Nishanth Menon <nm@ti.com>
>> ---
>> Ref:
>> v1: https://patchwork.kernel.org/patch/86793/
>> v2 changes:
>> 	removed BUG_ON entirely. instead have introduced int
>> 	return value allowing for board files which call to
>> 	handle the return results intelligently.
> 
> Thanks, I like this better.
> 
thx.. comments follow..

>>  arch/arm/mach-omap2/cpufreq34xx.c |   36 ++++++++++++++++++++++++++++++++----
>>  arch/arm/mach-omap2/omap3-opp.h   |    5 +++--
>>  2 files changed, 35 insertions(+), 6 deletions(-)
>>
>> diff --git a/arch/arm/mach-omap2/cpufreq34xx.c b/arch/arm/mach-omap2/cpufreq34xx.c
>> index 189c42e..01cf98f 100644
>> --- a/arch/arm/mach-omap2/cpufreq34xx.c
>> +++ b/arch/arm/mach-omap2/cpufreq34xx.c
[..]

>>  
>> -void __init omap3_pm_init_opp_table(void)
>> +int __init omap3_pm_init_opp_table(void)
>>  {
>> +	int i, r;
>>  	struct omap_opp_def **omap3_opp_def_list;
>>  	struct omap_opp_def *omap34xx_opp_def_list[] = {
>>  		omap34xx_mpu_rate_table,
>> @@ -122,12 +124,38 @@ void __init omap3_pm_init_opp_table(void)
>>  		omap36xx_l3_rate_table,
>>  		omap36xx_dsp_rate_table
>>  	};
>> +	enum opp_t omap3_opps[] = {
>> +		OPP_MPU,
>> +		OPP_L3,
>> +		OPP_DSP
>> +	};
> 
> Aren't these already defined in <plat/opp.h> ?
They are. but without using a array, I cant have a for loop ;).. i 
prefer for loops to replicating code thrice ;)..

if your question is on:
+#include "omap3-opp.h"
the reason is the header include makes sense to keep sparse happy + 
first time i built, there was'nt a crib from build when void became int, 
realized this was needed anyways.. shrug if you would like to split it 
out as a separate patch..

if your point was something else, I missed it.. :(
> 
>>  
>>  	omap3_opp_def_list = cpu_is_omap3630() ? omap36xx_opp_def_list :
>>  				omap34xx_opp_def_list;
>>  
>> -	BUG_ON(opp_init_list(OPP_MPU, omap3_opp_def_list[0]));
>> -	BUG_ON(opp_init_list(OPP_L3, omap3_opp_def_list[1]));
>> -	BUG_ON(opp_init_list(OPP_DSP, omap3_opp_def_list[2]));
>> +	for (i = 0; i < ARRAY_SIZE(omap3_opps); i++) {
>> +		r = opp_init_list(omap3_opps[i], omap3_opp_def_list[i]);
>> +		if (r)
>> +			break;
>> +	}
>> +	if (!r)
>> +		return 0;
>> +
>> +	/* Cascading error handling - disable all enabled OPPs */
>> +	pr_err("%s: Failed to register %d OPP type\n", __func__,
>> +		omap3_opps[i]);
>> +	i--;
>> +	while (i != -1) {
>> +		struct omap_opp *opp;
>> +		unsigned long freq = 0;
> 
> insert blank line
> 
thx..
>> +		while (!IS_ERR(opp = opp_find_freq_ceil(omap3_opps[i],
>> +							&freq))) {
> 
> for redability, would rather see the line-wrap avoided. 
> Just put the IS_ERR() on a separate line.
/me kicks myself for being lazy about this.. i guess i better kick it 
out and clean that loop out.. will do..

[..]

-- 
Regards,
Nishanth Menon

      reply	other threads:[~2010-04-20 23:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-20 19:49 [PM-WIP-OPP][PATCH 0/2 v2] opp layer cleanups Nishanth Menon
2010-04-20 19:49 ` [PM-WIP-OPP][PATCH 1/2 v2] omap3: pm: cpufreq: BUG_ON cleanup Nishanth Menon
2010-04-20 19:49   ` [PM-WIP-OPP][PATCH 2/2] omap: pm: opp: twl: use DIV_ROUND_UP Nishanth Menon
2010-04-20 23:42     ` Kevin Hilman
2010-04-20 23:41   ` [PM-WIP-OPP][PATCH 1/2 v2] omap3: pm: cpufreq: BUG_ON cleanup Kevin Hilman
2010-04-20 23:48     ` Nishanth Menon [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=4BCE3D49.20309@ti.com \
    --to=nm@ti.com \
    --cc=ambresh@ti.com \
    --cc=b-cousson@ti.com \
    --cc=eduardo.valentin@nokia.com \
    --cc=ext-phil.2.carmody@nokia.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=premi@ti.com \
    --cc=tero.kristo@nokia.com \
    --cc=thara@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.