All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: linux-omap <linux-omap@vger.kernel.org>
Cc: "Dasgupta, Romit" <romit@ti.com>,
	"Cousson, Benoit" <b-cousson@ti.com>,
	Eduardo Valentin <eduardo.valentin@nokia.com>,
	Kevin Hilman <khilman@deeprootsystems.com>,
	"Chikkature Rajashekar, Madhusudhan" <madhu.cr@ti.com>,
	Paul Walmsley <paul@pwsan.com>, "Premi, Sanjeev" <premi@ti.com>,
	"Shilimkar, Santosh" <santosh.shilimkar@ti.com>,
	"Aguirre, Sergio" <saaguirre@ti.com>,
	Tero Kristo <Tero.Kristo@nokia.com>,
	"Gopinath, Thara" <thara@ti.com>,
	"Sripathy, Vishwanath" <vishwanath.bs@ti.com>
Subject: Re: [PM-WIP-OPP][PATCH v4] omap: pm: Introducing enum for OPP types
Date: Thu, 28 Jan 2010 14:45:50 -0600	[thread overview]
Message-ID: <4B61F77E.1020900@ti.com> (raw)
In-Reply-To: <1264711201-16922-1-git-send-email-nm@ti.com>

Menon, Nishanth had written, on 01/28/2010 02:40 PM, the following:
> From: Romit Dasgupta <romit@ti.com>
> 
> Using omap_opp * to refer to domain types entails opp implementation
> into maintaining pointers outside the opp layer.
> 
> Since all we need is an identifier to a specific domain for
> query/operational purposes, we introduce enum for identifying OPP
> types instead of using opp layer's internal data structure pointer.
> 
> Currently, OMAP3 is the only silicon supporting the OPP layer, hence
> mpu_opps, l3_opps and dsp_opps are deprecated and replaced with
> OPP_MPU, OPP_L3 and OPP_DSP respectively.
> 
> Cc: Benoit Cousson <b-cousson@ti.com>
> Cc: Eduardo Valentin <eduardo.valentin@nokia.com>
> Cc: Kevin Hilman <khilman@deeprootsystems.com>
> Cc: Madhusudhan Chikkature Rajashekar <madhu.cr@ti.com>
> Cc: Nishanth Menon <nm@ti.com>
> Cc: Paul Walmsley <paul@pwsan.com>
> Cc: Sanjeev Premi <premi@ti.com>
> Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
> Cc: Sergio Alberto Aguirre Rodriguez <saaguirre@ti.com>
> Cc: Tero Kristo <Tero.Kristo@nokia.com>
> Cc: Thara Gopinath <thara@ti.com>
> Cc: Vishwanath Sripathy <vishwanath.bs@ti.com>
> 
> Signed-off-by: Romit Dasgupta <romit@ti.com>
arrgh.. forgot to add, anyways, for patchworks:
Acked-by: Nishanth Menon <nm@ti.com>

Tested also on SDP3430, SDP3630
> 
> ---
> Synopsys of changes:
> Rev 1: http://marc.info/?t=126330004800004&r=1&w=2
> Rev 2: http://marc.info/?t=126355341800003&r=1&w=2
> Rev 3: http://marc.info/?t=126408156100006&r=1&w=2
> Rev 4 specific changes Vs Rev 3:
>  * Multiple TI copyrights merged to a single one
>  * Couple of checkpatch warnings for multiple assignments fixed
>  * Cpufreq rates were reversed during initialization - fixed
>  * Rebased to pm-wip-opp branch as requested for rev 3.
> 
[...]
-- 
Regards,
Nishanth Menon

  reply	other threads:[~2010-01-28 20:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-28 20:40 [PM-WIP-OPP][PATCH v4] omap: pm: Introducing enum for OPP types Nishanth Menon
2010-01-28 20:45 ` Nishanth Menon [this message]
2010-02-04 19:36 ` 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=4B61F77E.1020900@ti.com \
    --to=nm@ti.com \
    --cc=Tero.Kristo@nokia.com \
    --cc=b-cousson@ti.com \
    --cc=eduardo.valentin@nokia.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=madhu.cr@ti.com \
    --cc=paul@pwsan.com \
    --cc=premi@ti.com \
    --cc=romit@ti.com \
    --cc=saaguirre@ti.com \
    --cc=santosh.shilimkar@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 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.