From: Sanjeev Premi <premi@ti.com>
To: linux-omap@vger.kernel.org
Cc: Sanjeev Premi <premi@ti.com>
Subject: [PATCHv1 0/1] omap3: pm: Delink OPP layer from cpufreq
Date: Mon, 31 May 2010 18:08:47 +0530 [thread overview]
Message-ID: <1275309527-25965-1-git-send-email-premi@ti.com> (raw)
The OPP layer is currently contained in CONFIG_CPU_FREQ.
When the ARM frequency is set via bootarg 'mpurate' the
OPP layer is required to:
- verify that specified mpurate is valid and available
in the OPP table.
- get voltage corresponding to specified frequency.
This is initial attempt to make OPP layer available without
cpufreq. Since, this is initial version, i am making changes
in board-omap3evm.c only. same change will be required in
other board files as well. Will do so in next version of
the patch.
I have also updated the OPP tables for OMAP3430 to include
support for 720MHz. It will be a separate patch when I submit
it next.
[1] http://marc.info/?l=linux-omap&m=127495955603835&w=2
Sanjeev Premi (1):
omap3: pm: Delink opp layer and cpufreq
arch/arm/mach-omap2/Makefile | 6 +-
arch/arm/mach-omap2/board-omap3evm.c | 2 +-
arch/arm/mach-omap2/cpufreq34xx.c | 164 --------------------------------
arch/arm/mach-omap2/omap3-opp.h | 20 ----
arch/arm/mach-omap2/opp34xx_data.c | 166 +++++++++++++++++++++++++++++++++
arch/arm/mach-omap2/pm34xx.c | 1 -
arch/arm/plat-omap/Makefile | 7 +-
arch/arm/plat-omap/cpu-omap.c | 47 +++++++++
arch/arm/plat-omap/include/plat/opp.h | 82 +---------------
arch/arm/plat-omap/opp.c | 46 ---------
10 files changed, 225 insertions(+), 316 deletions(-)
delete mode 100644 arch/arm/mach-omap2/cpufreq34xx.c
delete mode 100644 arch/arm/mach-omap2/omap3-opp.h
create mode 100644 arch/arm/mach-omap2/opp34xx_data.c
reply other threads:[~2010-05-31 12:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1275309527-25965-1-git-send-email-premi@ti.com \
--to=premi@ti.com \
--cc=linux-omap@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).