cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@dominikbrodowski.de>
To: Stelian Pop <stelian@popies.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	davej@codemonkey.org.uk, cpufreq@www.linux.org.uk
Subject: Re: [PATCH 2.6] cpufreq longrun driver fix
Date: Mon, 5 Apr 2004 19:38:35 +0200	[thread overview]
Message-ID: <20040405173835.GA7328@dominikbrodowski.de> (raw)
In-Reply-To: <20040405155012.GI2718@deep-space-9.dsnet>


[-- Attachment #1.1: Type: text/plain, Size: 911 bytes --]

On Mon, Apr 05, 2004 at 05:50:12PM +0200, Stelian Pop wrote:
> Hi,
> 
> My TM5600 Crusoe processor, found inside a Sony Vaio C1VE laptop,
> does not work with the longrun cpufreq driver.
> 
> Upon investigation, the reason is that trying to set the performance 
> to 80% in longrun_determine_freqs leaves the performance to 100%.
> The performance level, at least on this particular model, can be lowered
> only in 33% steps. And in order to put the performance to 66%, the
> code should try to set the barrier to 70%.
> 
> The following patch does even more, it tries every value from 80%
> to 10% in 10% steps, until it succeeds in lowering the performance.
> I'm not sure this is the best way to do it but in any case, 
> it works for me (and should continue to work for everybody else).

Patch looks good to me -- thanks, Stelian! 
Dave, could you merge it, please?

Thanks,
	Dominik
 

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
Cpufreq mailing list
Cpufreq@www.linux.org.uk
http://www.linux.org.uk/mailman/listinfo/cpufreq

  reply	other threads:[~2004-04-05 17:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-05 15:50 [PATCH 2.6] cpufreq longrun driver fix Stelian Pop
2004-04-05 17:38 ` Dominik Brodowski [this message]
2004-04-05 17:59   ` Dave Jones

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=20040405173835.GA7328@dominikbrodowski.de \
    --to=linux@dominikbrodowski.de \
    --cc=cpufreq@www.linux.org.uk \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stelian@popies.net \
    /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