From: Javi Merino <javi.merino@arm.com>
To: "myungjoo.ham@gmail.com" <myungjoo.ham@gmail.com>
Cc: "Linux PM list" <linux-pm@vger.kernel.org>,
"Ørjan Eide" <Orjan.Eide@arm.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>
Subject: Re: [PATCH 1/4] PM / devfreq: Add function to set max/min frequency
Date: Mon, 6 Jul 2015 09:47:36 +0100 [thread overview]
Message-ID: <20150706084736.GA2772@e104805> (raw)
In-Reply-To: <CAJ0PZbQgW3hPuk-PXWqUrVfYhM1MWHDrRDOQE9vGxkS1Wb=AGQ@mail.gmail.com>
On Sat, Jul 04, 2015 at 03:44:08AM +0100, MyungJoo Ham wrote:
> On Fri, Jul 3, 2015 at 9:58 PM, Javi Merino <javi.merino@arm.com> wrote:
> > From: Ørjan Eide <orjan.eide@arm.com>
> >
> > Factor out the logic to set minimum and maximum frequency for the device
> > so that it can be used by other parts of the kernel.
> >
> > Cc: MyungJoo Ham <myungjoo.ham@samsung.com>
> > Cc: Kyungmin Park <kyungmin.park@samsung.com>
> > Signed-off-by: Ørjan Eide <orjan.eide@arm.com>
>
> Dear Javi,
>
> Is there reasons to name the function "devfreq_qos_set_[min|max]"? not
> "devfreq_set_[min|max]"? The functions may be used by non-PM-qos
> components as well (e.g., thermal).
No, there are no reasons for those names. I'll rename them to
devfreq_set_[min|max]
> And I like the idea of using devfreq devices as cooling devices. :)
Yes, we would like to be able to use them as passive cooling devices,
like what we do with cpufreq for the cpus.
> ps. I will be on a trip starting hours later for 8 days and then in a
> military training for 3 days. Please expect that my responses during
> the next 11-12 days will be very slow.
No worries. Thanks,
Javi
next prev parent reply other threads:[~2015-07-06 8:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 12:58 [PATCH 0/4] Devfreq cooling device Javi Merino
2015-07-03 12:58 ` [PATCH 1/4] PM / devfreq: Add function to set max/min frequency Javi Merino
2015-07-04 2:44 ` MyungJoo Ham
2015-07-06 8:47 ` Javi Merino [this message]
2015-07-03 12:58 ` [PATCH 2/4] PM / devfreq: cache the last call to get_dev_status() Javi Merino
2015-07-04 3:15 ` MyungJoo Ham
2015-07-06 9:35 ` Javi Merino
2015-07-03 12:58 ` [PATCH 3/4] thermal: Add devfreq cooling Javi Merino
2015-07-03 12:58 ` [PATCH 4/4] devfreq_cooling: add trace information Javi Merino
2015-07-06 18:58 ` Steven Rostedt
2015-07-07 7:56 ` Javi Merino
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=20150706084736.GA2772@e104805 \
--to=javi.merino@arm.com \
--cc=Orjan.Eide@arm.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-pm@vger.kernel.org \
--cc=myungjoo.ham@gmail.com \
/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).