From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: myungjoo.ham@samsung.com
Cc: "Nishanth Menon" <nm@ti.com>, linux-pm <linux-pm@vger.kernel.org>,
"Rajagopal Venkat" <rajagopal.venkat@linaro.org>,
박경민 <kyungmin.park@samsung.com>, "Kevin Hilman" <khilman@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [for-next PATCH V2] PM / devfreq: Add sysfs node to expose available frequencies
Date: Wed, 31 Oct 2012 10:15:51 +0100 [thread overview]
Message-ID: <1711506.ZFBefezGp9@vostro.rjw.lan> (raw)
In-Reply-To: <3578820.552041351649466344.JavaMail.weblogic@epv6ml03>
On Wednesday, October 31, 2012 02:11:06 AM MyungJoo Ham wrote:
> > On Friday, October 26, 2012 06:16:36 AM MyungJoo Ham wrote:
> > > > devfreq governors such as ondemand are controlled by a min and
> > > > max frequency, while governors like userspace governor allow us
> > > > to set a specific frequency.
> > > > However, for the same specific device, depending on the SoC, the
> > > > available frequencies can vary.
> > > >
> > > > So expose the available frequencies as a snapshot over sysfs to
> > > > allow informed decisions.
> > > >
> > > > This was inspired by cpufreq framework's equivalent for similar
> > > > usage sysfs node: scaling_available_frequencies.
> > > >
> > > > Cc: Rajagopal Venkat <rajagopal.venkat@linaro.org>
> > > > Cc: MyungJoo Ham <myungjoo.ham@samsung.com>
> > > > Cc: Kyungmin Park <kyungmin.park@samsung.com>
> > > > Cc: "Rafael J. Wysocki" <rjw@sisk.pl>
> > > > Cc: Kevin Hilman <khilman@ti.com>
> > > > Cc: linux-pm@vger.kernel.org
> > > > Cc: linux-kernel@vger.kernel.org
> > > >
> > > > Signed-off-by: Nishanth Menon <nm@ti.com>
> > >
> > > Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>
> >
> > Are you going to handle this patch?
>
> Yes, I've just setup the git repository this week
> and I'm willing to handle this one.
>
> It is applied at
> http://git.kernel.org/?p=linux/kernel/git/mzx/devfreq.git;a=shortlog;h=refs/heads/for-rafael
OK
Please let me know when you want me to pull from your tree.
Please also note that the release of v3.7-rc6 is the deadline for non-bugfix
changes targeted at v3.8. :-)
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2012-10-31 9:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 2:11 MyungJoo Ham
2012-10-31 9:15 ` Rafael J. Wysocki [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-26 6:16 MyungJoo Ham
2012-10-31 0:45 ` Rafael J. Wysocki
[not found] <[for-next PATCH] PM / devfreq: Add sysfs node to expose available frequencies>
2012-10-26 0:48 ` Nishanth Menon
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=1711506.ZFBefezGp9@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=khilman@ti.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@samsung.com \
--cc=nm@ti.com \
--cc=rajagopal.venkat@linaro.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®