Date: Mon, 13 Feb 2012 17:45:34 +0100
To: Dave Jones <davej@redhat.com>
From: "N. Coesel" <nico@nctdev.nl>
Subject: Re: Cpufreq shutdown patch (kernel 2.6.35.3)
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <20120213162852.GA29947@redhat.com>
References: <CPSMTPM-CMT109lZGdO0011ecc5@CPSMTPM-CMT109.kpnxchange.com>
 <20120213162852.GA29947@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-ID: <CPSMTPM-CMT106gqGng00022093@CPSMTPM-CMT106.kpnxchange.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1350
Lines: 33

Dave,

At 17:28 13-2-2012, Dave Jones wrote:
>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 ?

This was on an IMX51 embedded platform but I'm quite sure the same 
problem can occur on other platforms as well. There has to be some 
way to allow an orderly shutdown of the low level cpufreq system 
without a cold reset.

Nico Coesel


o---------------------------------------------------------------o
|                       N C T  Developments                     |
|Innovative embedded solutions                                  |
o---------------------------------------------------------------o 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/