From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: myungjoo.ham@samsung.com
Cc: "Xiaoguang Chen" <chenxg@marvell.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"khilman@ti.com" <khilman@ti.com>,
박경민 <kyungmin.park@samsung.com>,
"mturquette@ti.com" <mturquette@ti.com>
Subject: Re: [PATCH] PM: devfreq: init performance/powersave governor
Date: Sun, 29 Apr 2012 23:09:36 +0200 [thread overview]
Message-ID: <201204292309.36959.rjw@sisk.pl> (raw)
In-Reply-To: <15852322.15281335501548956.JavaMail.weblogic@epml25>
On Friday, April 27, 2012, MyungJoo Ham wrote:
> > Performance and powersave governor's get_target_freq
> > is not called if driver chooses one of these two governors.
> > Add init function in governor profile to call update_devfreq
> > which will call get_target_freq subsequently.
> >
> > Signed-off-by: Xiaoguang Chen <chenxg@marvell.com>
> Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>
Applied to linux-pm/linux-next.
Thanks,
Rafael
> Hello Xiaoguang,
>
>
> Yes, if we do not call any QoS, min/max, OPP interfaces or enable polling, we need to call this at init. In fact, this is a bugfix patch.
>
> Thank you!
>
> Cheers!
> MyungJoo.
>
>
>
> > ---
> > drivers/devfreq/governor_performance.c | 7 +++++++
> > drivers/devfreq/governor_powersave.c | 7 +++++++
> > 2 files changed, 14 insertions(+), 0 deletions(-)
> >
> > diff --git a/drivers/devfreq/governor_performance.c b/drivers/devfreq/governor_performance.c
> > index 574a06b..af75ddd 100644
> > --- a/drivers/devfreq/governor_performance.c
> > +++ b/drivers/devfreq/governor_performance.c
> > @@ -10,6 +10,7 @@
> > */
> >
> > #include <linux/devfreq.h>
> > +#include "governor.h"
> >
> > static int devfreq_performance_func(struct devfreq *df,
> > unsigned long *freq)
> > @@ -25,8 +26,14 @@ static int devfreq_performance_func(struct devfreq *df,
> > return 0;
> > }
> >
> > +static int performance_init(struct devfreq *devfreq)
> > +{
> > + return update_devfreq(devfreq);
> > +}
> > +
> > const struct devfreq_governor devfreq_performance = {
> > .name = "performance",
> > + .init = performance_init,
> > .get_target_freq = devfreq_performance_func,
> > .no_central_polling = true,
> > };
> > diff --git a/drivers/devfreq/governor_powersave.c b/drivers/devfreq/governor_powersave.c
> > index d742d4a..fec0cdb 100644
> > --- a/drivers/devfreq/governor_powersave.c
> > +++ b/drivers/devfreq/governor_powersave.c
> > @@ -10,6 +10,7 @@
> > */
> >
> > #include <linux/devfreq.h>
> > +#include "governor.h"
> >
> > static int devfreq_powersave_func(struct devfreq *df,
> > unsigned long *freq)
> > @@ -22,8 +23,14 @@ static int devfreq_powersave_func(struct devfreq *df,
> > return 0;
> > }
> >
> > +static int powersave_init(struct devfreq *devfreq)
> > +{
> > + return update_devfreq(devfreq);
> > +}
> > +
> > const struct devfreq_governor devfreq_powersave = {
> > .name = "powersave",
> > + .init = powersave_init,
> > .get_target_freq = devfreq_powersave_func,
> > .no_central_polling = true,
> > };
>
next prev parent reply other threads:[~2012-04-29 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 4:39 MyungJoo Ham
2012-04-29 21:09 ` Rafael J. Wysocki [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-27 3:16 Xiaoguang Chen
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=201204292309.36959.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=chenxg@marvell.com \
--cc=khilman@ti.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@ti.com \
--cc=myungjoo.ham@samsung.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
all inboxes | Powered by JetHome®