From: Kevin Hilman <khilman@deeprootsystems.com>
To: Thara Gopinath <thara@ti.com>
Cc: linux-omap@vger.kernel.org, paul@pwsan.com, vishwanath.bs@ti.com,
sawant@ti.com, b-cousson@ti.com
Subject: Re: [PATCH 10/10] OMAP4: Add opp tables.
Date: Wed, 25 Aug 2010 16:24:52 -0700 [thread overview]
Message-ID: <1282778692.11841.68.camel@localhost> (raw)
In-Reply-To: <87y6bu8et9.fsf@deeprootsystems.com>
On Wed, 2010-08-25 at 16:15 -0700, Kevin Hilman wrote:
> Thara Gopinath <thara@ti.com> writes:
>
> > This patch adds OPP tables for OMAP4. A new file
> > opp44xx.c has been added to keep the OMAP4 opp tables
> > and the registeration of these tables with the generic
> > opp framework.
> >
> > Signed-off-by: Thara Gopinath <thara@ti.com>
> > ---
> > arch/arm/mach-omap2/Makefile | 2 +-
> > arch/arm/mach-omap2/opp44xx.h | 26 ++++++++++++
> > arch/arm/mach-omap2/opp44xx_data.c | 80 ++++++++++++++++++++++++++++++++++++
> > arch/arm/mach-omap2/pm.c | 6 ++-
> > 4 files changed, 112 insertions(+), 2 deletions(-)
> > create mode 100644 arch/arm/mach-omap2/opp44xx.h
> > create mode 100644 arch/arm/mach-omap2/opp44xx_data.c
> >
> > diff --git a/arch/arm/mach-omap2/Makefile b/arch/arm/mach-omap2/Makefile
> > index d46fbec..ebe3f36 100644
> > --- a/arch/arm/mach-omap2/Makefile
> > +++ b/arch/arm/mach-omap2/Makefile
> > @@ -51,7 +51,7 @@ obj-$(CONFIG_ARCH_OMAP2) += pm24xx.o
> > obj-$(CONFIG_ARCH_OMAP2) += sleep24xx.o
> > obj-$(CONFIG_ARCH_OMAP3) += pm34xx.o sleep34xx.o voltage.o \
> > cpuidle34xx.o
> > -obj-$(CONFIG_ARCH_OMAP4) += pm44xx.o voltage.o
> > +obj-$(CONFIG_ARCH_OMAP4) += pm44xx.o voltage.o opp44xx_data.o
> > obj-$(CONFIG_PM_DEBUG) += pm-debug.o
> > obj-$(CONFIG_OMAP_SMARTREFLEX) += sr_device.o smartreflex.o
> > obj-$(CONFIG_OMAP_SMARTREFLEX_CLASS3) += smartreflex-class3.o
> > diff --git a/arch/arm/mach-omap2/opp44xx.h b/arch/arm/mach-omap2/opp44xx.h
> > new file mode 100644
> > index 0000000..2cae9f3
> > --- /dev/null
> > +++ b/arch/arm/mach-omap2/opp44xx.h
>
> We don't really a new OMAP4-specific header for this. Let's just rename
> omap3-opp.h to omap-opp.h and put both init functions there.
>
> I'll update the pm-opp branch accordingly.
s/pm-opp/pm-cpufreq/
Actually, what I did was drop the header all together and just add the
definition to pm.c.
Kevin
next prev parent reply other threads:[~2010-08-25 23:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 11:16 [PATCH 00/10] OMAP4: Smartreflex and Voltage layer support Thara Gopinath
2010-08-18 11:16 ` [PATCH 01/10] OMAP4: PM debugfs support Thara Gopinath
2010-08-18 11:16 ` [PATCH 02/10] OMAP4: OPP framework support Thara Gopinath
2010-08-18 11:16 ` [PATCH 03/10] OMAP4: Add the new voltage to vsel calculation formula Thara Gopinath
2010-08-18 11:16 ` [PATCH 04/10] OMAP4: Extend clock data Thara Gopinath
2010-08-18 11:16 ` [PATCH 05/10] OMAP4: Adding voltage driver support Thara Gopinath
2010-08-25 23:08 ` Kevin Hilman
2010-08-18 11:16 ` [PATCH 06/10] OMAP4: hwmod: Add inital data for smartreflex modules Thara Gopinath
2010-08-18 11:16 ` [PATCH 07/10] OMAP4: Adding dev atrributes to OMAP4 smartreflex hwmod data Thara Gopinath
2010-08-18 11:16 ` [PATCH 08/10] OMAP4: Smartreflex framework extensions Thara Gopinath
2010-08-25 23:12 ` Kevin Hilman
2010-08-26 5:12 ` Shilimkar, Santosh
2010-08-18 11:16 ` [PATCH 09/10] OMAP4: Enabling smartrefles class 3 driver Thara Gopinath
2010-08-18 11:16 ` [PATCH 10/10] OMAP4: Add opp tables Thara Gopinath
2010-08-25 23:15 ` Kevin Hilman
2010-08-25 23:24 ` Kevin Hilman [this message]
2010-08-25 22:58 ` [PATCH 00/10] OMAP4: Smartreflex and Voltage layer support 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=1282778692.11841.68.camel@localhost \
--to=khilman@deeprootsystems.com \
--cc=b-cousson@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=sawant@ti.com \
--cc=thara@ti.com \
--cc=vishwanath.bs@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