From: Romit Dasgupta <romit@ti.com>
To: "eduardo.valentin@nokia.com" <eduardo.valentin@nokia.com>
Cc: ext Kevin Hilman <khilman@deeprootsystems.com>,
"Menon, Nishanth" <nm@ti.com>,
"Keski-Saari Juha.1 (EXT-Teleca/Helsinki)"
<ext-juha.1.keski-saari@nokia.com>,
"Cousson, Benoit" <b-cousson@ti.com>,
Linux-OMAP <linux-omap@vger.kernel.org>
Subject: Re: [PATCHv3 1/1] OMAP3: PM: move omap opp layer from pm34xx.c
Date: Wed, 20 Jan 2010 17:30:05 +0530 [thread overview]
Message-ID: <4B56F045.4040708@ti.com> (raw)
In-Reply-To: <20100120115407.GG12231@esdhcp037198.research.nokia.com>
Eduardo Valentin wrote:
> On Wed, Jan 20, 2010 at 12:14:59PM +0100, ext Romit Dasgupta wrote:
>>> From: Eduardo Valentin <eduardo.valentin@nokia.com>
>>>
>>> OMAP OPP layer functions now have dependencies of CONFIG_CPU_FREQ only.
>>>
>>> With this patch, omap opp layer now has its compilation flags
>>> bound to CONFIG_CPU_FREQ. Also its code has been removed from pm34xx.c.
>>>
>>> A new file has been created to contain cpu freq code related to
>>> OMAP3: cpufreq34xx.c.
>>>
>>> Signed-off-by: Eduardo Valentin <eduardo.valentin@nokia.com>
>> NAK also for the following non-working kernel (smartreflex without cpufreq).
>
> Then this is a problem of dependency with smartreflex and cpufreq. In this case
> better to solve this other problem with another patch. This patch is to rip off
> cpufreq code from pm34xx, as stated in the above description.
In that case the right fix should
1) __not__ include opp.h for non cpufreq builds
OR
2) If it includes opp.h the functions for getting current opp
should abstract out the right mechanism to get current frequency/voltage from
the chip/power IC.
>
> And sorry, I didn't get your boot log (if you intended to put it, as you said
> "following non-working kernel"
>
Actually I meant for the following non-working kernel __configuration__. I do
not have boot logs!
next prev parent reply other threads:[~2010-01-20 12:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 10:39 [PATCHv3 1/1] OMAP3: PM: move omap opp layer from pm34xx.c Eduardo Valentin
2010-01-20 11:13 ` Romit Dasgupta
2010-01-20 11:51 ` Eduardo Valentin
2010-01-20 11:52 ` Romit Dasgupta
2010-01-20 11:14 ` Romit Dasgupta
2010-01-20 11:54 ` Eduardo Valentin
2010-01-20 12:00 ` Romit Dasgupta [this message]
2010-01-20 12:40 ` Eduardo Valentin
2010-01-20 12:44 ` Romit Dasgupta
2010-01-20 12:49 ` Eduardo Valentin
2010-01-20 12:54 ` Romit Dasgupta
2010-01-20 14:20 ` Eduardo Valentin
2010-01-21 7:16 ` Romit Dasgupta
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=4B56F045.4040708@ti.com \
--to=romit@ti.com \
--cc=b-cousson@ti.com \
--cc=eduardo.valentin@nokia.com \
--cc=ext-juha.1.keski-saari@nokia.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