From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: MyungJoo Ham <myungjoo.ham@samsung.com>
Cc: Len Brown <len.brown@intel.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Kyungmin Park <kyungmin.park@samsung.com>,
linux-pm@lists.linux-foundation.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH v5 0/3] DEVFREQ, DVFS Framework for Non-CPU Devices.
Date: Wed, 10 Aug 2011 23:09:25 +0200 [thread overview]
Message-ID: <201108102309.25274.rjw@sisk.pl> (raw)
In-Reply-To: <1312794188-9823-1-git-send-email-myungjoo.ham@samsung.com>
On Monday, August 08, 2011, MyungJoo Ham wrote:
> For a usage example, please look at
> http://git.infradead.org/users/kmpark/linux-2.6-samsung/shortlog/refs/heads/devfreq
>
> In the above git tree, DVFS (dynamic voltage and frequency scaling) mechanism
> is applied to the memory bus of Exynos4210 for Exynos4210-NURI boards.
> In the example, the LPDDR2 DRAM frequency changes between 133, 266, and 400MHz
> and other related clocks simply follow the determined DDR RAM clock.
>
> The DEVFREQ driver for Exynos4210 memory bus is at
> /arch/arm/mach-exynos4/devfreq_bus.c in the git tree.
>
> In the dd (writing and reading 360MiB) test with NURI board, the memory
> throughput was not changed (the performance is not deteriorated) while
> the SoC power consumption has been reduced by 1%. When the memory access
> is not that intense while the CPU is heavily used, the SoC power consumption
> has been reduced by 6%. The power consumption has been compared with the
> case using the conventional Exynos4210 CPUFREQ driver, which sets memory
> bus frequency according to the CPU core frequency. Besides, when the CPU core
> running slow and the memory access is intense, the performance (memory
> throughput) has been increased by 11% (with higher SoC power consumption of
> 5%). The tested governor is "simple-ondemand".
>
> MyungJoo Ham (3):
> PM: Introduce DEVFREQ: generic DVFS framework with device-specific
> OPPs
> PM / DEVFREQ: add basic governors
> PM / DEVFREQ: add sysfs interface
>
> Documentation/ABI/testing/sysfs-devices-power | 45 ++
> drivers/base/power/Makefile | 1 +
> drivers/base/power/devfreq.c | 555 +++++++++++++++++++++++++
> drivers/base/power/opp.c | 9 +
> include/linux/devfreq.h | 111 +++++
> kernel/power/Kconfig | 34 ++
> 6 files changed, 755 insertions(+), 0 deletions(-)
> create mode 100644 drivers/base/power/devfreq.c
> create mode 100644 include/linux/devfreq.h
Are there still any objections to this version of the patchset?
Rafael
prev parent reply other threads:[~2011-08-10 21:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-08 9:03 [PATCH v5 0/3] DEVFREQ, DVFS Framework for Non-CPU Devices MyungJoo Ham
2011-08-08 9:03 ` [PATCH v5 1/3] PM: Introduce DEVFREQ: generic DVFS framework with device-specific OPPs MyungJoo Ham
2011-08-11 1:00 ` Turquette, Mike
2011-08-17 9:40 ` MyungJoo Ham
2011-08-08 9:03 ` [PATCH v5 2/3] PM / DEVFREQ: add basic governors MyungJoo Ham
2011-08-11 1:35 ` Turquette, Mike
2011-08-16 8:52 ` MyungJoo Ham
2011-08-16 18:11 ` Turquette, Mike
2011-08-17 7:32 ` MyungJoo Ham
2011-08-08 9:03 ` [PATCH v5 3/3] PM / DEVFREQ: add sysfs interface MyungJoo Ham
2011-08-08 9:53 ` [PATCH v5 0/3] DEVFREQ, DVFS Framework for Non-CPU Devices MyungJoo Ham
2011-08-08 21:35 ` Greg KH
2011-08-10 21:09 ` Rafael J. Wysocki [this message]
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=201108102309.25274.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=gregkh@suse.de \
--cc=kyungmin.park@samsung.com \
--cc=len.brown@intel.com \
--cc=linux-pm@lists.linux-foundation.org \
--cc=myungjoo.ham@samsung.com \
--cc=tglx@linutronix.de \
/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).