All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: "N. Coesel" <nico@nctdev.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Cpufreq shutdown patch (kernel 2.6.35.3)
Date: Mon, 13 Feb 2012 11:28:53 -0500	[thread overview]
Message-ID: <20120213162852.GA29947@redhat.com> (raw)
In-Reply-To: <CPSMTPM-CMT109lZGdO0011ecc5@CPSMTPM-CMT109.kpnxchange.com>

On Thu, Jan 19, 2012 at 10:18:10PM +0100, N. Coesel wrote:
 
 > I've found a problem in drivers/cpufreq/cpufreq.c. The driver does 
 > not execute the exit member of the low level driver when shutting 
 > down for a reboot (reset). This potentially leaves the power supply 
 > at a too low voltage to boot the system properly. The patch below 
 > adds a shutdown function which executes the exit member of the low 
 > level driver which allows a system to be properly prepared for a reset.

I'm curious what hardware you saw this problem on ?

I've just seen a report on an x86 system which looks like it might
be solved by this.
https://bugzilla.redhat.com/show_bug.cgi?id=789964

 > --- drivers/cpufreq/cpufreq.c.orig      2010-08-20 20:55:55.000000000 +0200
 > +++ drivers/cpufreq/cpufreq.c   2012-01-19 21:50:46.000000000 +0100
 > @@ -1431,11 +1431,34 @@ fail:
 >          return ret;
 >   }
 > 
 > +
 > +static int cpufreq_shutdown(struct sys_device *sysdev)
 > +{
 > +       struct cpufreq_policy *cpu_policy;
 > +       int cpu = sysdev->id;
 > +       int ret =0;
 > +
 > +       if (!cpu_online(cpu))
 > +               return 0;
 > +
 > +       cpu_policy = cpufreq_cpu_get(cpu);
 > +       if (!cpu_policy)
 > +               return -EINVAL;
 > +
 > +//     printk("cpufreq_shutdown %d \n", cpu);
 > +       if (cpufreq_driver->exit)
 > +               ret = cpufreq_driver->exit(cpu_policy);
 > +
 > +       return ret;
 > +}
 > +
 > +
 >   static struct sysdev_driver cpufreq_sysdev_driver = {
 >          .add            = cpufreq_add_dev,
 >          .remove         = cpufreq_remove_dev,
 >          .suspend        = cpufreq_suspend,
 >          .resume         = cpufreq_resume,
 > +       .shutdown = cpufreq_shutdown,
 >   };

I'll queue this up, with the whitespace fixed, and commented out line removed.

	Dave


  reply	other threads:[~2012-02-13 16:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-19 21:18 Cpufreq shutdown patch (kernel 2.6.35.3) N. Coesel
2012-02-13 16:28 ` Dave Jones [this message]
2012-02-13 16:35   ` Dave Jones
2012-02-14 14:03     ` Kay Sievers
2012-02-13 16:45   ` N. Coesel

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=20120213162852.GA29947@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nico@nctdev.nl \
    /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.