From: francesco.virlinzi@st.com (Francesco VIRLINZI)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-pm] Montreal Linux Power Management Mini-Summit, July 13, 2009 - Meeting Notes
Date: Thu, 03 Sep 2009 16:50:47 +0200 [thread overview]
Message-ID: <4A9FD7C7.7070301@st.com> (raw)
In-Reply-To: <20090902215832.GB21292@n2100.arm.linux.org.uk>
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?
>
>
next prev parent reply other threads:[~2009-09-03 14:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.00.0905211430220.4390@localhost.localdomain>
[not found] ` <alpine.LFD.2.00.0907301801240.17818@localhost.localdomain>
2009-09-01 22:22 ` Montreal Linux Power Management Mini-Summit, July 13, 2009 - Meeting Notes Linus Walleij
2009-09-02 2:25 ` Bill Gatliff
2009-09-02 8:36 ` [linux-pm] " Francesco VIRLINZI
2009-09-02 21:44 ` Linus Walleij
2009-09-02 21:58 ` Russell King - ARM Linux
2009-09-03 14:50 ` Francesco VIRLINZI [this message]
2009-09-03 17:12 ` Russell King - ARM Linux
2009-09-03 20:15 ` Linus Walleij
2009-09-03 21:28 ` Woodruff, Richard
2009-09-04 7:34 ` Francesco VIRLINZI
2009-10-18 17:28 ` Linus Walleij
2009-10-19 7:44 ` Francesco VIRLINZI
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=4A9FD7C7.7070301@st.com \
--to=francesco.virlinzi@st.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).