From: Kevin Hilman <khilman@deeprootsystems.com>
To: "G, Manjunath Kondaiah" <manjugk@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: new PM branch: OPP layer included
Date: Mon, 26 Apr 2010 09:51:33 -0700 [thread overview]
Message-ID: <87iq7eupgq.fsf@deeprootsystems.com> (raw)
In-Reply-To: <E0D41E29EB0DAC4E9F3FF173962E9E94026F6E303D@dbde02.ent.ti.com> (Manjunath Kondaiah G.'s message of "Mon\, 26 Apr 2010 18\:27\:42 +0530")
"G, Manjunath Kondaiah" <manjugk@ti.com> writes:
> Kevin,
> This merge has broken omap zoom3 build.
>
> Error log:
> In file included from arch/arm/plat-omap/include/plat/omap-pm.h:21,
> from arch/arm/mach-omap2/hsmmc.c:19:
> arch/arm/plat-omap/include/plat/opp.h: In function 'opp_find_freq_exact':
> arch/arm/plat-omap/include/plat/opp.h:255: error: implicit declaration of function 'ERR_PTR'
>
Thanks for the report. Looks like zoom3_defconfig doesn't have
CPUFreq enabled which is why I didn't see this with
omap3_pm_defconfig.
Disabling CPUfreq led to a couple other compile warnings which I've
fixed up in the original patches in the pm-opp branch.
Pushed a new PM branch with these fixes.
Kevin
>
>> -----Original Message-----
>> From: linux-omap-owner@vger.kernel.org
>> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of Kevin Hilman
>> Sent: Saturday, April 24, 2010 4:54 AM
>> To: linux-omap@vger.kernel.org
>> Subject: new PM branch: OPP layer included
>>
>> Hello,
>>
>> I just pushed a new PM branch. I did a bunch of reordering and
>> restructuring of branches to include the OPP layer (more on this
>> below.)
>>
>>
>> OPP layer:
>>
>> pm-wip-opp branch gone, merged into PM branch
>>
>> What was in pm-wip-opp has now been broken up into a set of patches
>> that can be combined and queued for upstream (pm-opp branch) as well
>> as sets of patches for SR and SRF which are now on their respective
>> branches (pm-sr, pm-srf)
>>
>> Next step is to combine the patches in pm-opp branch into a sensible
>> series that can be submitted for the next merge window.
>>
>>
>> Smart Reflex:
>>
>> Thara's v3 series available as pm-wip-sr. This is now based directly
>> on the new PM branch instead of on pm-wip-opp.
>>
>> NOTE: the hwmod patches are now merged into l-o (omap-fixes branch)
>> so they are no longer in pm-wip-sr.
>>
>> I didn't get to reviewing this series yet, but did test it out a bit
>> on top of thenew PM branch. I gave this some basic testing on n900
>> and Zoom3 (required a u-boot update first) but basic OPP changes from
>> userspace governor worked on both.
>>
>>
>> SRF:
>>
>> This is still included in the PM branch (pm-srf branch), but will be
>> removed from the official PM branch. It will be maintained as a
>> separate branch for a short time (1 month max) and then dropped.
>> Anyone else who wants to continue maintenance of SRF is free to do so.
>>
>>
>> Kevin
>> --
>> To unsubscribe from this list: send the line "unsubscribe
>> linux-omap" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
next prev parent reply other threads:[~2010-04-26 16:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 23:23 new PM branch: OPP layer included Kevin Hilman
2010-04-26 12:57 ` G, Manjunath Kondaiah
2010-04-26 16:51 ` Kevin Hilman [this message]
2010-05-04 17:43 ` 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=87iq7eupgq.fsf@deeprootsystems.com \
--to=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=manjugk@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.