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 00/10] OMAP4: Smartreflex and Voltage layer support
Date: Wed, 25 Aug 2010 15:58:47 -0700 [thread overview]
Message-ID: <87zkwa9u54.fsf@deeprootsystems.com> (raw)
In-Reply-To: <1282130191-9062-1-git-send-email-thara@ti.com> (Thara Gopinath's message of "Wed, 18 Aug 2010 16:46:21 +0530")
Thara Gopinath <thara@ti.com> writes:
> From: thara gopinath <thara@ti.com>
>
> This patch series adds support for OMAP4 support in the
> smartreflex and voltage layer. The series involves extensions
> to voltage layer and smartreflex layer for supporting OMAP4.
> In addition it involves changes to pm debugfs layer to support
> OMAP4 so that smartreflex and voltage debug entries can be
> viewed, changes in opp layer so that opp layer gets enabled
> for OMAP4, some changes in OMAP4 clock database and finally
> addition of OMAP4 opp tables.
> All these patches might not be dependent on voltage and
> smartreflex layer but is required for the correct
> functionality of these layers for OMAP4.
>
> This series in based off origin/pm-opp branch off
> Kevin Hilman's PM tree which is effectively 2.6.35 with
> basic opp support added. But for this series to compile
> and work properly one will have to apply the following
> additional patches in the below mentioned order before
> applying this series.
> https://patchwork.kernel.org/patch/119544/
this one under discussion
> https://patchwork.kernel.org/patch/117347/
> https://patchwork.kernel.org/patch/117348/
> https://patchwork.kernel.org/patch/117349/
these 3 are in Benoit's pm-wip/hwmods-omap4 branch
> http://marc.info/?l=linux-omap&m=128162263809748&w=2
this is in pm-fixes
> https://patchwork.kernel.org/patch/119854/
ok, but needs respin
> all 5 patches from origin/pm-cpufreq branch off Kevin's pm tree
> http://marc.info/?l=linux-omap&m=128170725127719&w=2
> - all eight patches in this series
This is a mess to track manually, It *really* would be nice if you could
share this on a git tree, or demonstrate how to reproduce this using
public git trees.
For example, I created a working baseline to apply this using
git checkout -b tmp/sr-v2 pm-opp
git merge pm-cpufreq
git merge pm-fixes
git merge benoit/pm-wip/hwmods-omap4 (minor conflict to resolve)
Kevin
> This patch series has been tested on OMAP4430 SDP with omap3_defconfig
> with the following menuconfig options enabled
> System type -> TI OMAP Implementations -> Smartreflex Support
> System type -> TI OMAP Implementations ->
> Class 3 mode of Smartreflex Implementation
>
> Benoit Cousson (1):
> OMAP4: hwmod: Add inital data for smartreflex modules.
>
> Thara Gopinath (9):
> OMAP4: PM debugfs support
> OMAP4: OPP framework support
> OMAP4: Add the new voltage to vsel calculation formula
> OMAP4: Extend clock data.
> OMAP4: Adding voltage driver support
> OMAP4: Adding dev atrributes to OMAP4 smartreflex hwmod data
> OMAP4: Smartreflex framework extensions
> OMAP4: Enabling smartrefles class 3 driver.
> OMAP4: Add opp tables.
>
> arch/arm/mach-omap2/Makefile | 2 +-
> arch/arm/mach-omap2/board-4430sdp.c | 2 +
> arch/arm/mach-omap2/clock44xx_data.c | 40 ++++-
> arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 220 +++++++++++++++++++++++++
> arch/arm/mach-omap2/opp44xx.h | 26 +++
> arch/arm/mach-omap2/opp44xx_data.c | 80 +++++++++
> arch/arm/mach-omap2/pm-debug.c | 53 +++++-
> arch/arm/mach-omap2/pm.c | 6 +-
> arch/arm/mach-omap2/smartreflex.c | 7 +-
> arch/arm/mach-omap2/sr_device.c | 21 ++-
> arch/arm/mach-omap2/voltage.c | 246 +++++++++++++++++++++++++++-
> arch/arm/plat-omap/Kconfig | 2 +-
> arch/arm/plat-omap/Makefile | 1 +
> arch/arm/plat-omap/include/plat/control.h | 12 ++
> arch/arm/plat-omap/include/plat/voltage.h | 20 ++-
> arch/arm/plat-omap/opp_twl_tps.c | 8 +
> 16 files changed, 721 insertions(+), 25 deletions(-)
> create mode 100644 arch/arm/mach-omap2/opp44xx.h
> create mode 100644 arch/arm/mach-omap2/opp44xx_data.c
prev parent reply other threads:[~2010-08-25 22:58 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
2010-08-25 22:58 ` Kevin Hilman [this message]
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=87zkwa9u54.fsf@deeprootsystems.com \
--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