From: Linus Walleij <linus.ml.walleij@gmail.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Linux Power Management List <linux-pm@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Len Brown <lenb@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: 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 prev parent reply other threads:[~2009-09-01 22:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 19:12 Montreal Linux Power Management Mini-Summit -- July 13, 2009 Len Brown
2009-05-24 11:35 ` Rafael J. Wysocki
2009-05-28 5:36 ` Magnus Damm
2009-05-28 9:32 ` [linux-pm] " Paul Mundt
2009-07-30 22:04 ` Montreal Linux Power Management Mini-Summit, July 13, 2009 - Meeting Notes Len Brown
2009-09-01 22:22 ` Linus Walleij [this message]
2009-09-02 2:25 ` Bill Gatliff
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=lenb@kernel.org \
--cc=lethal@linux-sh.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.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
all inboxes | Powered by JetHome®