From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nishanth Menon Subject: Re: Question on OPP table handling Date: Tue, 6 Oct 2009 07:04:19 -0500 Message-ID: <4ACB3243.409@ti.com> References: <1254420194-4757-1-git-send-email-premi@ti.com> <4AC76810.1040206@gmail.com> <87ws39zsn4.fsf@deeprootsystems.com> <4ACA2A86.7060300@ti.com> <74583B8642AB8841B30447520659FCA9DDAEF27A@dnce01.ent.ti.com> <4ACB2DAD.1090200@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from bear.ext.ti.com ([192.94.94.41]:56554 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932216AbZJFME5 (ORCPT ); Tue, 6 Oct 2009 08:04:57 -0400 In-Reply-To: Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: "Dasgupta, Romit" Cc: "Premi, Sanjeev" , "Cousson, Benoit" , Kevin H , "linux-omap@vger.kernel.org" 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