From mboxrd@z Thu Jan 1 00:00:00 1970 From: Igor Stoppa Subject: Re: Few enhancement ideas Date: Fri, 15 Jul 2005 16:11:33 +0300 Message-ID: <1121433093.27159.9.camel@localhost> References: <1121277175.6338.105.camel@localhost> <20050714215607.GA16613@best.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============30335601501435994==" Return-path: In-Reply-To: <20050714215607.GA16613@best.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: "ext Leo L. Schwab" Cc: linux-pm@lists.osdl.org List-Id: linux-pm@vger.kernel.org --===============30335601501435994== Content-Type: text/plain Content-Transfer-Encoding: 7bit On Thu, 2005-07-14 at 14:56 -0700, ext Leo L. Schwab wrote: [snip] > When you were implementing the framework, did you have any thoughts > about where the initial clock frequencies "should" come from? It sounds > like a policy issue, and therefore compiling it into the kernel (as you've > done in your OMAP implementation) is The Wrong Thing. But it's not at all > clear where else it could go. We agree on that: it looks like a policy and the way to provide the means to configure it is something that should be discussed. We are still considering a few implementation options. igor > > Again, my thanks. It was tons of help. > > Schwab > _______________________________________________ > linux-pm mailing list > linux-pm@lists.osdl.org > https://lists.osdl.org/mailman/listinfo/linux-pm --===============30335601501435994== Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --===============30335601501435994==--