From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Menon, Nishanth" <nm@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 00/10 V5] omap3: pm: introduce support for 3630 OPPs
Date: Thu, 17 Dec 2009 08:10:29 -0800 [thread overview]
Message-ID: <87tyvp60p6.fsf@deeprootsystems.com> (raw)
In-Reply-To: <4B29A401.1050001@ti.com> (Nishanth Menon's message of "Thu\, 17 Dec 2009 08\:52\:41 +0530")
"Menon, Nishanth" <nm@ti.com> writes:
> Kevin Hilman said the following on 12/17/2009 04:07 AM:
>> Kevin Hilman <khilman@deeprootsystems.com> writes:
>>
>>
>>> Nishanth Menon <nm@ti.com> writes:
>>>
>>>
>>>> Hi,
>>>> Thanks for all the comments. Here are the *changed* patches since V5
>>>>
>>>> What changed in V5:
>>>> * review comment incorporated
>>>> * vsel is deprecated now
>>>> * I seem to have hit a checkpatch.pl bug as in
>>>> http://lkml.org/lkml/2009/12/11/573, made me check the usage
>>>> of __deprecated for struct params, and used it in a
>>>> consistent manner to functions..
>>>> * More warnings added to build :( (deprecated ones ofcourse)
>>>> * removed OMAP_OPP_DEF_TERMINATOR
>>>> * 3430 and 3630 patches changed as a result
>>>>
>> [...]
>>
>>
>>> 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].
>>>
>>> The branch is called 'pm-wip-opp' and I have rebased onto the PM
>>> branch I pushed today.
>>>
>>
>>
> Thanks Kevin.
>
>> I forgot to mention that I've also pushed the patch for removing OPP
>> interface from the OMAP PM layer[1] to the work-in-progress OPP
>> branch.
>>
>> Kevin
>>
>> [1] http://marc.info/?l=linux-omap&m=125917007423545&w=2
>>
> Reg [1]
> What is the point of having
> void __init omap2_init_common_hw(struct omap_sdrc_params *sdrc_cs0,
> struct omap_sdrc_params *sdrc_cs1,
> struct omap_opp *mpu_opps,
> struct omap_opp *dsp_opps,
> struct omap_opp *l3_opps)
>
> Why have mpu_opps, dsp_opps and l3_opps anymore? those parameters are
> unused anymore. the patch should have changed omap2_init_common_hw and
> related board calls - am I right?
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.
Kevin
next prev parent reply other threads:[~2009-12-17 16:10 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 [this message]
2009-12-18 10:26 ` Romit Dasgupta
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=87tyvp60p6.fsf@deeprootsystems.com \
--to=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