From mboxrd@z Thu Jan 1 00:00:00 1970 From: Francesco VIRLINZI Subject: Re: [linux-pm] Montreal Linux Power Management Mini-Summit, July 13, 2009 - Meeting Notes Date: Thu, 03 Sep 2009 16:50:47 +0200 Message-ID: <4A9FD7C7.7070301@st.com> References: <63386a3d0909011522m7a175d3eyb3bbe8a29a5fd104@mail.gmail.com> <4A9E2EA7.8080700@st.com> <20090902215832.GB21292@n2100.arm.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20090902215832.GB21292@n2100.arm.linux.org.uk> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-arm-kernel-bounces@lists.infradead.org Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Russell King - ARM Linux Cc: Linus Walleij , Paul Mundt , Linux Power Management List , linux-arm-kernel@lists.infradead.org List-Id: linux-pm@vger.kernel.org Hi Russel Sorry I don't know the clkdev API. In any case the CF, I will present, tracks the relationship between device and clock. During any clock changing the CF checks if all the device agree the new rate before the clock is changed. How does the clkdev work? Regards Francesco On 09/02/2009 11:58 PM, Russell King - ARM Linux wrote: > On Wed, Sep 02, 2009 at 10:36:55AM +0200, Francesco VIRLINZI wrote: > >> Hi Linus >> FYI: >> I'm going to present a generic linux clock framework during the CELF-Europe >> @ >> http://www.embeddedlinuxconference.com/elc_europe09/sessions.html#Virlinzi >> > How does this differ from the clk API with clkdev that we already have? > >