cpufreq.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinson Lee <vlee@twopensource.com>
To: stable@vger.kernel.org
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
	Shatil Rafitullah <srafiullah@twopensource.com>,
	Len Brown <len.brown@intel.com>,
	Ross Lagerwall <rosslagerwall@gmail.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: [stable request <=3.5] acpi-cpufreq: set current frequency based on target P-State
Date: Thu, 19 Dec 2013 18:14:12 -0800	[thread overview]
Message-ID: <CAHTgTXW_M6U6oCgek-K45O2PeS71RpjUyZeJ8f5C97odvk09MA@mail.gmail.com> (raw)

Hi.

Is commit 8673b83bf2f013379453b4779047bf3c6ae387e4 "acpi-cpufreq: set
current frequency based on target P-State" applicable to kernels
before 3.8?

We found that this patch allows the kernel to control P-states on
3.4.74 on some platforms. However, other platforms were able to change
P-states even without this patch.

Cheers,
Vinson

             reply	other threads:[~2013-12-20  2:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-20  2:14 Vinson Lee [this message]
2013-12-20  8:19 ` [stable request <=3.5] acpi-cpufreq: set current frequency based on target P-State Ross Lagerwall
2014-03-25 22:04   ` [stable request <=3.7] " Vinson Lee
2014-03-25 22:04     ` [PATCH] " Vinson Lee
2014-03-25 22:18     ` [stable request <=3.7] " rosslagerwall
2014-03-25 22:53       ` Vinson Lee
2014-03-26  7:22         ` rosslagerwall
2014-04-11 16:05       ` Greg KH
2014-03-31  8:50     ` Luís Henriques

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=CAHTgTXW_M6U6oCgek-K45O2PeS71RpjUyZeJ8f5C97odvk09MA@mail.gmail.com \
    --to=vlee@twopensource.com \
    --cc=cpufreq@vger.kernel.org \
    --cc=len.brown@intel.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rjw@rjwysocki.net \
    --cc=rosslagerwall@gmail.com \
    --cc=srafiullah@twopensource.com \
    --cc=stable@vger.kernel.org \
    --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 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 read-only IMAP folder(s) and NNTP newsgroup(s).