From: MyungJoo Ham <myungjoo.ham@samsung.com>
To: Alexandre Courbot <gnurou@gmail.com>,
Arto Merilainen <amerilainen@nvidia.com>
Cc: 박경민 <kyungmin.park@samsung.com>,
"tomeu.vizoso@collabora.com" <tomeu.vizoso@collabora.com>,
"javier.martinez@collabora.co.uk"
<javier.martinez@collabora.co.uk>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
"srasal@nvidia.com" <srasal@nvidia.com>
Subject: Re: Re: [RFC RESEND 0/3] Add watermark support to devfreq
Date: Tue, 16 Dec 2014 06:42:38 +0000 (GMT) [thread overview]
Message-ID: <1134564356.176631418712156720.JavaMail.weblogic@epmlwas06d> (raw)
Alexandre Courbot:
>
> MyungJoo, the issue of having this feature in the core vs. having it
> as a devfreq "extension" aside, do you agree with the core idea? An
> informl ack for the idea would allow us to start leveraging this for
> the ACTMON driver. With a concrete user it will make it easier for
> everyone to understand how the pieces should fit together.
Yes, I love the idea of event/interrupt-driven DVFS and I agree with
the core idea. The remaining concern is that the current "implementation"
might be too invasive to the subsystem while it does not need to be as
a governor can always choose not to poll. And the other issues are
quite minor as well.
Actually, it appears that next-generations of some architectures
(I think I cannot publically say which and when) are going to support
this for general peripherals on the bus and the CPU soon.
Cheers,
MyungJoo
>
reply other threads:[~2014-12-16 6:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1134564356.176631418712156720.JavaMail.weblogic@epmlwas06d \
--to=myungjoo.ham@samsung.com \
--cc=amerilainen@nvidia.com \
--cc=gnurou@gmail.com \
--cc=grant.likely@linaro.org \
--cc=javier.martinez@collabora.co.uk \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=srasal@nvidia.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=tomeu.vizoso@collabora.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