From: linux@baker-net.org.uk (Adam Baker)
To: linux-arm-kernel@lists.infradead.org
Subject: Kirkwood CPU Freq driver
Date: Tue, 28 May 2013 22:36:13 +0100 [thread overview]
Message-ID: <51A5234D.9030100@baker-net.org.uk> (raw)
In-Reply-To: <20130526180513.GF31290@titan.lakedaemon.net>
On 26/05/13 19:05, Jason Cooper wrote:
> On Sun, May 26, 2013 at 10:36:14AM +0200, Andrew Lunn wrote:
>> On Sat, May 25, 2013 at 10:32:04PM +0100, Adam Baker wrote:
>>> I've been trying to test Andrew Lunn's work creating a CPU Idle
>>> driver for Kirkwood.
>>
>> Thanks for testing this. I must admit, i never tested it once the
>> first rc came out. I clearly should of, because its broken. It was a
>> three part patch series, and only part 1/3 made it in. Hence the
>> issues you are seeing.
>>
>> Jason, please can you pick up:
>>
>> https://patchwork.kernel.org/patch/2051401/
>> https://patchwork.kernel.org/patch/2080931/
>
> Yep, got them in now. Sorry for the mix up.
>
I've now tested with the first of these patches applied and the changes
from the second added to my .config
To get it to work I had to follow the instructions in the Documentation
to add the cpus entry to kirkwood.dtsi so I'll post that as a patch in a
day or two but after doing that I have a working cpufreq driver.
Measuring the power consumption of my NAS server I observed a slight
reduction in power consumption when the clock rate was reduced. I
haven't yet measured for long enough to get an accurate measurement but
it looks like maybe 1/4 W power saving.
Feel free to add
Tested-by: Adam Baker <linux@baker-net.org.uk>
Regards
Adam
next prev parent reply other threads:[~2013-05-28 21:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-25 21:32 Kirkwood CPU Freq driver Adam Baker
2013-05-26 8:36 ` Andrew Lunn
2013-05-26 18:05 ` Jason Cooper
2013-05-28 21:36 ` Adam Baker [this message]
2013-05-28 21:51 ` Andrew Lunn
2013-05-30 23:19 ` Adam Baker
2013-05-31 5:33 ` Andrew Lunn
2013-05-29 0:58 ` Jason Cooper
2013-05-29 19:34 ` Jason Cooper
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=51A5234D.9030100@baker-net.org.uk \
--to=linux@baker-net.org.uk \
--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).