All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Brandewie <dirk.brandewie@gmail.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: dirk.brandewie@gmail.com,
	Linux PM list <linux-pm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Patrick Marlier <patrick.marlier@gmail.com>,
	Dirk Brandewie <dirk.j.brandewie@intel.com>
Subject: Re: [PATCH v2 2/2] intel_pstate: Set core to min P state during core offline
Date: Tue, 18 Mar 2014 08:01:47 -0700	[thread overview]
Message-ID: <53285FDB.40102@gmail.com> (raw)
In-Reply-To: <CAOh2x=kFC5cwdYVgFCwNgqZAwWaE-CFQoyYizBuv1W6MOnQ9DA@mail.gmail.com>

On 03/17/2014 10:44 PM, Viresh Kumar wrote:
> On Sat, Mar 15, 2014 at 2:33 AM,  <dirk.brandewie@gmail.com> wrote:
>> +
>>   static int intel_pstate_cpu_init(struct cpufreq_policy *policy)
>>   {
>>          struct cpudata *cpu;
>> @@ -818,7 +824,7 @@ static struct cpufreq_driver intel_pstate_driver = {
>>          .setpolicy      = intel_pstate_set_policy,
>>          .get            = intel_pstate_get,
>>          .init           = intel_pstate_cpu_init,
>> -       .exit           = intel_pstate_cpu_exit,
>> +       .stop           = intel_pstate_cpu_stop,
>
> Probably, keep exit as is and only change P-state in stop(). So that
> allocation of resources happen in init() and they are freed in exit()?
>
I looked at doing just that but it junked up the code.  if stop() is called
during PREPARE then init() will be called via __cpufreq_add_dev() in the ONLINE
and DOWN_FAILED case. So once stop() is called the driver will be ready for
init() to be called exactly like when exit() is called.



  reply	other threads:[~2014-03-18 15:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAKQMxzQhVz0QT6tV0PKFjXXpYpDbtnOBH=miARoeQhrvs2TKFQ@mail.gmail.com>
     [not found] ` <5320D05F.7050304@gmail.com>
     [not found]   ` <5320D12B.4040303@gmail.com>
2014-03-13  0:07     ` intel_pstate: Lower p-state when putting down CPU Rafael J. Wysocki
2014-03-13  4:56       ` Viresh Kumar
2014-03-13 21:39         ` Rafael J. Wysocki
2014-03-14 21:03       ` [PATCH v2 0/2] Add exit_prepare callback to the cpufreq_driver interface dirk.brandewie
2014-03-14 21:03         ` [PATCH v2 1/2] cpufreq: Add exit_prepare callback to " dirk.brandewie
2014-03-15  2:04           ` Rafael J. Wysocki
2014-03-18  5:43             ` Viresh Kumar
2014-03-14 21:03         ` [PATCH v2 2/2] intel_pstate: Set core to min P state during core offline dirk.brandewie
2014-03-18  5:44           ` Viresh Kumar
2014-03-18 15:01             ` Dirk Brandewie [this message]
2014-03-18 18:52               ` Srivatsa S. Bhat
2014-03-18 19:44                 ` Dirk Brandewie
2014-03-18 20:15                   ` Srivatsa S. Bhat
2014-03-19  5:20                   ` Viresh Kumar
2014-03-19 15:32                     ` Dirk Brandewie
2014-03-18 17:22         ` [PATCH v3 0/2] Add stop callback to the cpufreq_driver interface dirk.brandewie
2014-03-18 17:22           ` [PATCH 1/2] cpufreq: Add stop callback to " dirk.brandewie
2014-03-19  5:04             ` Viresh Kumar
2014-03-18 17:22           ` [PATCH 2/2] intel_pstate: Set core to min P state during core offline dirk.brandewie
2014-03-18 19:08             ` Srivatsa S. Bhat
2014-03-18 19:08           ` [PATCH v3 0/2] Add stop callback to the cpufreq_driver interface Srivatsa S. Bhat
2014-03-18 19:25             ` Dirk Brandewie
2014-03-18 20:04               ` Srivatsa S. Bhat
2014-03-19  0:53               ` Rafael J. Wysocki
2014-03-19  5:33                 ` Viresh Kumar
2014-03-19 14:01                   ` Rafael J. Wysocki
2014-03-19 13:49                     ` Viresh Kumar
2014-03-19 14:25                       ` Rafael J. Wysocki

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=53285FDB.40102@gmail.com \
    --to=dirk.brandewie@gmail.com \
    --cc=dirk.j.brandewie@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=patrick.marlier@gmail.com \
    --cc=rjw@rjwysocki.net \
    --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.