public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@deeprootsystems.com>
To: "Cousson, Benoit" <b-cousson@ti.com>
Cc: "Dasgupta, Romit" <romit@ti.com>, "Menon, Nishanth" <nm@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PM-WIP-OPP][PATCH] OPP: Introduces enum for addressing different OPP types
Date: Tue, 12 Jan 2010 11:26:22 -0800	[thread overview]
Message-ID: <87wrzn86qp.fsf@deeprootsystems.com> (raw)
In-Reply-To: <74583B8642AB8841B30447520659FCA9E73BDA08@dnce01.ent.ti.com> (Benoit Cousson's message of "Tue\, 12 Jan 2010 18\:36\:37 +0100")

"Cousson, Benoit" <b-cousson@ti.com> writes:

> Hi Kevin,
>
>>From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
>>owner@vger.kernel.org] On Behalf Of Kevin Hilman
>>Sent: Tuesday, January 12, 2010 6:19 PM
>>To: Dasgupta, Romit
>>Cc: Menon, Nishanth; linux-omap@vger.kernel.org
>>Subject: Re: [PM-WIP-OPP][PATCH] OPP: Introduces enum for addressing
>>different OPP types
>>
>>Romit Dasgupta <romit@ti.com> writes:
>>
>>> Introduces enum for identifying OPP types. This helps in querying the OPP
>>> layer by passing the type of OPP (enum types) and gets away from
>>maintaining
>>> the pointer to the OPP data list outside the OPP layer.
>>>
>>> Signed-off-by: Romit Dasgupta <romit@ti.com>
>>
>>I like this idea... but I have some questions about how we should
>>cleanly handle SMP and future SoCs.
>
> Well, it is better than what we have today, but maybe not super
> scalable for next device. This information is completely device
> dependant and should not be in a plat-omap file.  In that case, it
> will be tricky to have an enum per devices because it will prevent
> multiple omap build.  That for that reason that I think we might use
> hwmod to identify the relevant scalable IPs, instead of yet another
> identifier for something that is IP related.

OK.  Let's take this approach for now, and after hwmods get
stabilized/merged we can consider alternate per-SoC ways to handle
this.

Thanks,

Kevin

  reply	other threads:[~2010-01-12 19:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12 12:39 [PM-WIP-OPP][PATCH] OPP: Introduces enum for addressing different OPP types Romit Dasgupta
2010-01-12 17:19 ` Nishanth Menon
2010-01-12 17:19 ` Kevin Hilman
2010-01-12 17:36   ` Cousson, Benoit
2010-01-12 19:26     ` Kevin Hilman [this message]
2010-01-13 10:31   ` Romit Dasgupta
2010-01-12 17:57 ` Menon, Nishanth
2010-01-13 10:41   ` Romit Dasgupta
2010-01-13 12:54     ` Nishanth Menon
2010-01-13 13:22       ` Romit Dasgupta
2010-01-15 10:35         ` Nishanth Menon
2010-01-15 10:42           ` Romit Dasgupta
2010-01-15 10:56             ` Nishanth Menon
2010-01-13 14: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=87wrzn86qp.fsf@deeprootsystems.com \
    --to=khilman@deeprootsystems.com \
    --cc=b-cousson@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=romit@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