From: 함명주 <myungjoo.ham@samsung.com>
To: "Saravana Kannan" <skannan@codeaurora.org>,
박경민 <kyungmin.park@samsung.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4] PM / devfreq: Add possible_frequencies device attribute
Date: Mon, 21 Jul 2014 01:42:41 +0000 (GMT) [thread overview]
Message-ID: <2979470.179111405906960960.JavaMail.weblogic@epml01> (raw)
Sender : Saravana Kannan<skannan@codeaurora.org>
Title : [PATCH v4] PM / devfreq: Add possible_frequencies device attribute
>
> Some devices use freq_table instead of OPP. For those devices, the
> available_frequencies sysfs file shows up empty. So, add a
> possible_frequencies attribute/syfs file that list all the possible
> frequencies.
>
> For devices that use OPP, the output of this file will match
> available_frequencies. It may change in the future to show all OPP
> frequencies -- even the disabled ones.
>
> Signed-off-by: Saravana Kannan
Looks Good.
Signed-off-by: MyungJoo Ham <myungjoo.ham@samsung.com>
I'll rebase and merge into devfreq-next when I get back (I can only access the Internet via mobile phones until Wed this week.)
I'll move this sysfs entry to .../stat along with stat sysfs and make it conditional (appears only when stat is available)
Cheers,
MyungJoo.
--
MyungJoo Ham (함명주), PHD
Frontier CS Lab, Software Center
Samsung Electronics
Cell: +82-10-6714-2858
next reply other threads:[~2014-07-21 1:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 1:42 함명주 [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-17 0:50 [PATCH v3] PM / devfreq: Add possible_frequencies device attribute MyungJoo Ham
2014-07-19 0:15 ` [PATCH v4] " Saravana Kannan
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=2979470.179111405906960960.JavaMail.weblogic@epml01 \
--to=myungjoo.ham@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=skannan@codeaurora.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).