From: Bruno Ducrot <ducrot@poupinou.org>
To: davej@redhat.com
Cc: cpufreq@lists.linux.org.uk, linux-acpi@vger.kernel.org
Subject: Re: [PATCH] allow the highest frequency if bios think so.
Date: Tue, 21 Nov 2006 14:51:54 +0100 [thread overview]
Message-ID: <20061121135154.GL4945@poupinou.org> (raw)
In-Reply-To: <20061121103042.GI4945@poupinou.org>
On Tue, Nov 21, 2006 at 11:30:42AM +0100, Bruno Ducrot wrote:
> Hi all,
>
> processor_perflib.c::acpi_processor_ppc_notifier() check if the value
> returned by the processor's _PPC method is 0 and return failed if so.
> This is wrong since 0 indicate that the bios think the processor can go
> to the highest frequency. This patch for example fix the HP NX 6125 to
> allow its highest frequency to be available.
>
> Signed-off-by: Bruno Ducrot <ducrot@poupinou.org>
>
> --- linux-2.6.19-rc6/drivers/acpi/processor_perflib.c 2006/11/21 10:18:39 1.1
> +++ linux-2.6.19-rc6/drivers/acpi/processor_perflib.c 2006/11/21 10:18:55
> @@ -83,8 +83,6 @@ static int acpi_processor_ppc_notifier(s
> goto out;
>
> ppc = (unsigned int)pr->performance_platform_limit;
> - if (!ppc)
> - goto out;
>
> if (ppc > pr->performance->state_count)
BTW I'm wondering if this check should be :
if (ppc >= pr->performance->state_count)
> goto out;
--
Bruno Ducrot
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2006-11-21 13:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 10:30 [PATCH] allow the highest frequency if bios think so Bruno Ducrot
2006-11-21 11:04 ` Peter Clifton
2006-11-21 11:11 ` Bruno Ducrot
2006-11-29 7:25 ` Maciej Rutecki
2006-11-21 13:51 ` Bruno Ducrot [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-21 15:08 Pallipadi, Venkatesh
2006-11-21 16:35 ` Bruno Ducrot
2006-11-21 17:03 ` 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=20061121135154.GL4945@poupinou.org \
--to=ducrot@poupinou.org \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
--cc=linux-acpi@vger.kernel.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