From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: "Turquette, Mike" <mturquette@ti.com>
Cc: Len Brown <len.brown@intel.com>,
Greg Kroah-Hartman <gregkh@suse.de>,
Kyungmin Park <kyungmin.park@samsung.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-pm@lists.linux-foundation.org
Subject: Re: [PATCH v4 0/3] DEVFREQ, DVFS framework for non-CPU devices
Date: Fri, 29 Jul 2011 11:10:41 +0200 [thread overview]
Message-ID: <201107291110.41801.rjw@sisk.pl> (raw)
In-Reply-To: <CAJOA=zNpmQpCyh0ow2q6gUTxkLMcWDsoMOaQEGzV4Sw__BszHg@mail.gmail.com>
On Friday, July 29, 2011, Turquette, Mike wrote:
> On Thu, Jul 28, 2011 at 3:10 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> > On Friday, July 15, 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.
> >>
> >> MyungJoo Ham (3):
> >> PM: Introduce DEVFREQ: generic DVFS framework with device-specific
> >> OPPs
> >> PM / DEVFREQ: add example governors
> >> PM / DEVFREQ: add sysfs interface (including user tickling)
> >
> > OK, I'm going to take the patches for 3.2.
>
> Have any other platforms signed up to use this mechanism to manage
> their peripheral DVFS?
Not that I know of, but one initial user is sufficient for me.
So if you have anything _against_ the patches, please speak up.
Thanks,
Rafael
next prev parent reply other threads:[~2011-07-29 9:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 8:11 [PATCH v4 0/3] DEVFREQ, DVFS framework for non-CPU devices MyungJoo Ham
2011-07-15 8:11 ` [PATCH v4 1/3] PM: Introduce DEVFREQ: generic DVFS framework with device-specific OPPs MyungJoo Ham
2011-08-02 18:45 ` Kevin Hilman
2011-08-03 8:06 ` MyungJoo Ham
2011-08-02 21:56 ` Kevin Hilman
2011-08-03 6:02 ` MyungJoo Ham
2011-07-15 8:11 ` [PATCH v4 2/3] PM / DEVFREQ: add example governors MyungJoo Ham
2011-07-15 8:11 ` [PATCH v4 3/3] PM / DEVFREQ: add sysfs interface (including user tickling) MyungJoo Ham
2011-06-09 17:11 ` Pavel Machek
2011-07-19 2:14 ` MyungJoo Ham
2011-07-28 22:10 ` [PATCH v4 0/3] DEVFREQ, DVFS framework for non-CPU devices Rafael J. Wysocki
2011-07-29 4:46 ` Turquette, Mike
2011-07-29 9:10 ` Rafael J. Wysocki [this message]
2011-07-30 1:02 ` Turquette, Mike
2011-07-30 21:23 ` Rafael J. Wysocki
2011-08-01 21:47 ` Turquette, Mike
2011-08-01 6:22 ` MyungJoo Ham
2011-08-01 22:01 ` Turquette, Mike
2011-08-02 7:17 ` MyungJoo Ham
2011-08-02 22:02 ` Kevin Hilman
2011-08-03 7:03 ` MyungJoo Ham
2011-08-03 17:31 ` Turquette, Mike
2011-08-03 18:33 ` Kevin Hilman
2011-08-04 8:15 ` MyungJoo Ham
2011-08-04 21:59 ` Turquette, Mike
2011-08-05 6:18 ` MyungJoo Ham
2011-08-08 19:13 ` Turquette, Mike
2011-08-09 5:27 ` MyungJoo Ham
2011-08-11 1:28 ` Turquette, Mike
2011-08-17 10:07 ` MyungJoo Ham
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=201107291110.41801.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=mturquette@ti.com \
--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