From: linus.ml.walleij@gmail.com (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: Montreal Linux Power Management Mini-Summit, July 13, 2009 - Meeting Notes
Date: Wed, 2 Sep 2009 00:22:14 +0200 [thread overview]
Message-ID: <63386a3d0909011522m7a175d3eyb3bbe8a29a5fd104@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0907301801240.17818@localhost.localdomain>
2009/7/31 Len Brown <lenb@kernel.org>:
> A Linux Power Management "mini-summit" was held on July 13th, 2009 -
> on the first day of the Montreal Linux Symposium.
> (...)
> SH running cpufreq on top of clock framework
> ? ? ? ?cpufreq has notifiers, clock framework does not
Hm! Paul can you elaborate on what that was about.
I've felt a need for clock notifiers and we've cheated by using
CPUfreq because it so happens that the clocking in system-wide
and whenever the CPU freq change so may the other clocks.
But if I put code into a PrimeCell MMC/SPI/I2C driver or whatever and
use CPUfreq that's very unelegant, and for other platforms where
the CPU freq don't change when this particular device clk freq
change plain misleading.
A clk pre/postchange notifier pair would really help and would
make for elegant drivers that can handle clock freq transitions.
Has anyone poked at this?
Linus Walleij
next parent reply other threads:[~2009-09-01 22:22 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 ` Linus Walleij [this message]
2009-09-02 2:25 ` Montreal Linux Power Management Mini-Summit, July 13, 2009 - Meeting Notes 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
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=63386a3d0909011522m7a175d3eyb3bbe8a29a5fd104@mail.gmail.com \
--to=linus.ml.walleij@gmail.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).