From: Nishanth Menon <nm@ti.com>
To: "Dasgupta, Romit" <romit@ti.com>
Cc: "Premi, Sanjeev" <premi@ti.com>,
"Cousson, Benoit" <b-cousson@ti.com>,
Kevin H <khilman@deeprootsystems.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Question on OPP table handling
Date: Tue, 6 Oct 2009 07:04:19 -0500 [thread overview]
Message-ID: <4ACB3243.409@ti.com> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59301DDC0936B@dbde02.ent.ti.com>
Dasgupta, Romit had written, on 10/06/2009 07:00 AM, the following:
>> Couple of opinions on why a list with disabled/invalid marker might not
>> make sense as a grand unified OPP table:
>> a) it is no better than a list implementation
>> b) it is a waste of memory.
> [Romit] Put all the OPP tables for different OPPs in __initdata. Copy the runtime detected CPU's OPP table in memory. Others get discarded!
>
I like this approach.. takers?
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2009-10-06 12:04 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 18:03 [PATCHv2 1/1] OMAP3: PM: Functions to get freq from opp and vice-versa Sanjeev Premi
2009-10-03 15:04 ` Question on OPP table handling Nishanth Menon
2009-10-05 13:09 ` Premi, Sanjeev
2009-10-05 16:56 ` Kevin Hilman
2009-10-05 17:19 ` Nishanth Menon
2009-10-06 8:06 ` Shilimkar, Santosh
2009-10-06 8:44 ` Premi, Sanjeev
2009-10-06 9:19 ` Shilimkar, Santosh
2009-10-06 8:42 ` Cousson, Benoit
2009-10-06 8:52 ` Premi, Sanjeev
2009-10-06 11:44 ` Nishanth Menon
2009-10-06 12:00 ` Dasgupta, Romit
2009-10-06 12:04 ` Nishanth Menon [this message]
2009-10-06 12:10 ` Cousson, Benoit
2009-10-06 12:14 ` Dasgupta, Romit
2009-10-06 12:52 ` Cousson, Benoit
2009-10-09 0:41 ` Nishanth Menon
2009-10-06 12:21 ` Dasgupta, Romit
2009-10-06 12:43 ` Shilimkar, Santosh
2009-10-06 13:29 ` Kevin Hilman
2009-10-09 15:19 ` [PATCHv2 1/1] OMAP3: PM: Functions to get freq from opp and vice-versa 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=4ACB3243.409@ti.com \
--to=nm@ti.com \
--cc=b-cousson@ti.com \
--cc=khilman@deeprootsystems.com \
--cc=linux-omap@vger.kernel.org \
--cc=premi@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 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.