All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Thomas Renninger <trenn@suse.de>
Cc: Jacob Shin <jacob.shin@amd.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [PATCH V3 2/2] cpufreq: AMD "frequency sensitivity feedback" powersave bias for ondemand governor
Date: Tue, 2 Apr 2013 23:01:24 +0200	[thread overview]
Message-ID: <20130402210124.GI17675@pd.tnic> (raw)
In-Reply-To: <2932884.BNCEuERbdR@skinner.arch.suse.de>

On Tue, Apr 02, 2013 at 10:51:51PM +0200, Thomas Renninger wrote:
> Yep, if you want anyone to make use of this, it should better get
> embedded in more general, at least general ondemand code.

Yeah, it all sounds like we want to enable this by default on systems
which support it. Maybe with an off-switch for people who want plain
ondemand decisions.

The remaining systems with ripped out powersave_bias would get plain
ondemand governor decisions. Provided, of course, nobody uses
powersave_bias and the functionality doesn't make any sense anyway.

Thanks.

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2013-04-02 21:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 18:11 [PATCH V3 0/2] cpufreq: ondemand: add AMD specific powersave bias Jacob Shin
2013-04-02 18:11 ` Jacob Shin
2013-04-02 18:11 ` [PATCH V3 1/2] cpufreq: ondemand: allow custom powersave_bias_target handler to be registered Jacob Shin
2013-04-02 18:11   ` Jacob Shin
2013-04-02 19:24   ` Borislav Petkov
2013-04-03  5:12   ` Viresh Kumar
2013-04-02 18:11 ` [PATCH V3 2/2] cpufreq: AMD "frequency sensitivity feedback" powersave bias for ondemand governor Jacob Shin
2013-04-02 18:11   ` Jacob Shin
2013-04-02 19:23   ` Borislav Petkov
2013-04-02 19:23     ` Borislav Petkov
2013-04-02 20:03     ` Jacob Shin
2013-04-02 20:03       ` Jacob Shin
2013-04-02 20:03       ` Jacob Shin
2013-04-02 20:40       ` Borislav Petkov
2013-04-02 20:51       ` Thomas Renninger
2013-04-02 21:01         ` Borislav Petkov [this message]
2013-04-03 16:53           ` Jacob Shin
2013-04-03 16:53             ` Jacob Shin
2013-04-03 17:04             ` Borislav Petkov
2013-04-03 17:17               ` Jacob Shin
2013-04-03 17:17                 ` Jacob Shin
2013-04-03 17:30                 ` Borislav Petkov

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=20130402210124.GI17675@pd.tnic \
    --to=bp@alien8.de \
    --cc=cpufreq@vger.kernel.org \
    --cc=jacob.shin@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=trenn@suse.de \
    --cc=viresh.kumar@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.