From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: Nishanth Menon <nm@ti.com>, linux-pm <linux-pm@vger.kernel.org>
Cc: "Rajagopal Venkat" <rajagopal.venkat@linaro.org>,
박경민 <kyungmin.park@samsung.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
"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: Fri, 26 Oct 2012 06:16:36 +0000 (GMT) [thread overview]
Message-ID: <16123783.160701351232196244.JavaMail.weblogic@epv6ml08> (raw)
> 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>
next reply other threads:[~2012-10-26 6:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-26 6:16 MyungJoo Ham [this message]
2012-10-31 0:45 ` [for-next PATCH V2] PM / devfreq: Add sysfs node to expose available frequencies Rafael J. Wysocki
-- strict thread matches above, loose matches on Subject: below --
2012-10-31 2:11 MyungJoo Ham
2012-10-31 9:15 ` 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=16123783.160701351232196244.JavaMail.weblogic@epv6ml08 \
--to=myungjoo.ham@samsung.com \
--cc=khilman@ti.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rajagopal.venkat@linaro.org \
--cc=rjw@sisk.pl \
/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).